[Mod-security-developers] [JIRA] Closed: (MODSEC-134) Do not track original values for the TX variables

[Ivan R. (JIRA) <no...@mo...>]

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

Ivan Ristic closed MODSEC-134.
------------------------------

    Resolution: Won't Fix

It's not important, really. I submitted this in February 2010, and it's only a minor performance optimization.

> Do not track original values for the TX variables
> -------------------------------------------------
>
>                 Key: MODSEC-134
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-134
>             Project: ModSecurity
>          Issue Type: Bug
>      Security Level: Normal
>    Affects Versions: 2.5.11
>            Reporter: Ivan Ristic
>            Assignee: Breno Silva Pinto
>             Fix For: 2.6.3
>
>
> I've noticed that setvar tracks relative changes:
> [9] Setting variable: tx.exp=%{TIME_EPOCH}
> [9] Resolved macro %{TIME_EPOCH} to: 1264578415
> [9] Set variable "tx.exp" to "1264578415".
> [9] Setting variable: tx.exp=-%{IP.CREATE_TIME}
> [9] Recorded original collection variable: tx.exp = "1264578415"
> [9] Resolved macro %{IP.CREATE_TIME} to: 1264578269
> [9] Relative change: exp=1264578415-1264578269
> [9] Set variable "tx.exp" to "146".
> That's needed for persistent collections, but not for TX.

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