[Mod-security-developers] [JIRA] Resolved: (MODSEC-300) ModSec Variable "DURATION" comes in milliseconds, while the Apache equivalent (%D) comes in microseconds as come the various PERF_PHASE variables in ModSec

[Breno S. P. (JIRA) <no...@mo...>]

     [ https://www.modsecurity.org/tracker/browse/MODSEC-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Breno Silva Pinto resolved MODSEC-300.
--------------------------------------

    Resolution: Fixed

> ModSec Variable "DURATION" comes in milliseconds, while the Apache equivalent (%D) comes in microseconds as come the various PERF_PHASE variables in ModSec
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MODSEC-300
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-300
>             Project: ModSecurity
>          Issue Type: Bug
>      Security Level: Normal
>          Components: Core
>    Affects Versions: 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5
>         Environment: Any
>            Reporter: Christian Folini
>            Assignee: Breno Silva Pinto
>             Fix For: 2.7.0
>
>
> The use of milliseconds for the Variable "DURATION" is an anomaly. 
> Apache itself uses microseconds for its %D variable (=Duration; see http://httpd.apache.org/docs/2.4/mod/mod_log_config.html).
> The various PERF variables in ModSec also use microseconds. (see http://sourceforge.net/apps/mediawiki/mod-security/index.php?title=Reference_Manual#PERF_PHASE1)
> Googling for "SecRule Duration" (https://www.google.ch/search?q="SecRule+Duration") reveals, that there are no published recipes using this variable. So changing this should not break too many things.
> The variable is set in re_variables.c with the help of apr_time_msec. Using apr_time_usec should do the trick.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira