Hello David,

Did you try ?

SecRuleUpdateTargetById 981318 "!ARGS:email,REQUEST_URI"

REQUEST_FILENAME already exists in the rule, so it will be no included.

Thanks

Breno

On Mon, Jul 30, 2012 at 9:56 AM, David R <rewt@linux-elite.org> wrote:
Dear Breno,

At first many thanks for this fast reply!

I can confirm this is working but this doe snot explain why i can't include a
REQUEST_URI to be more "precise".

Do you know any workaround that should work to be able to set also the
REQUEST_URI or REQUEST_FILENAME with that rule ?

Please let me know.
Kind regards,

David



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
mod-security-users mailing list
mod-security-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mod-security-users
Commercial ModSecurity Rules and Support from Trustwave's SpiderLabs:
http://www.modsecurity.org/projects/commercial/rules/
http://www.modsecurity.org/projects/commercial/support/