Re: Reason for case discrpency in variable names?
Andrew Howe <[email protected]> Fri, 29 Oct 2021 11:12:35 +0200
| Newsgroups | gmane.comp.apache.mod-security.user |
|---|---|
| Message-ID | <CA+NVLm4jCqGwskJNcnvBUcBR6HH+RL6uarxGi4rk65TTf6qNhA@mail.gmail.com> |
Hello Quinn,
The syntax for *using* variables is subtly different to the syntax for
*defining* variables, e.g.
setvar:tx.my_thing
versus
SecRule TX:my_thing
At least in the Core Rule Set project, we try to emphasise this
difference by using upper-case letters for the collection (e.g. TX)
when *using* a variable and lower-case letters (e.g. tx) when
*defining* a variable. In addition, lower-case letters are used for
variables in both cases. (See:
https://github.com/coreruleset/coreruleset/blob/v3.4/dev/CONTRIBUTING.md#variable-naming-conventions).
It looks like the example from the ModSecurity Reference Manual you
mentioned also changes the case of the variable name, for even more
emphasis.
Hopefully that answers your question.
Thanks,
Andrew
_______________________________________________
mod-security-users mailing list
[email protected]
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/