Re: [Mod-security-developers] Directive Names in NginX and IIS

[Felipe C. <FC...@tr...>]

Hi Christian,


Good question. The directive names in all versions (including nginx, iis and libModSecurity)
should be treated in the same way.


Here is the piece of code from libModSecurity for this specific directive:
https://github.com/SpiderLabs/ModSecurity/blob/libmodsecurity/src/parser/seclang-scanner.ll#L80

Notice the `?i:’, this is the key to make the directive case insensitive.

Br.,

Felipe “Zimmerle” Costa
Security Researcher, Lead Developer ModSecurity.

Trustwave | SMART SECURITY ON DEMAND
www.trustwave.com <http://www.trustwave.com/>








On 9/5/16, 10:39 AM, "Christian Folini" <chr...@ne...> wrote:

>Hi there,
>
>The sourcecode defines the function
>SecGeoLookupDB.
>However, all references in the documentation point to
>SecGeoLookupDb.
>
>Apache directives are case insensitive. So this is no big deal.
>But what's the matter on NginX and IIS. Do both variants work there?
>Or has the documentation to be adopted. And how about v3?
>
>Ahoj,
>
>Christian
>
>
>--
>https://scanmail.trustwave.com/?c=4062&d=yfXN15-hXAx9I7-upzFOf1_QB-ShRJISXePxha0Rmw&s=5&u=https%3a%2f%2fwww%2efeistyduck%2ecom%2ftraining%2fmodsecurity-training-course
>mailto:chr...@ne...
>twitter: @ChrFolini
>
>------------------------------------------------------------------------------
>_______________________________________________
>mod-security-developers mailing list
>mod...@li...
>https://scanmail.trustwave.com/?c=4062&d=yfXN15-hXAx9I7-upzFOf1_QB-ShRJISXef1iqtFyg&s=5&u=https%3a%2f%2flists%2esourceforge%2enet%2flists%2flistinfo%2fmod-security-developers
>ModSecurity Services from Trustwave's SpiderLabs:
>https://www.trustwave.com/spiderLabs.php

________________________________

This transmission may contain information that is privileged, confidential, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is strictly prohibited. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format.