[Mod-security-developers] [JIRA] Resolved: (MODSEC-218) Expanding directive scope locations

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

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

Breno Silva Pinto resolved MODSEC-218.
--------------------------------------

    Resolution: Fixed

> Expanding directive scope locations
> -----------------------------------
>
>                 Key: MODSEC-218
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-218
>             Project: ModSecurity
>          Issue Type: Improvement
>      Security Level: Normal
>          Components: Configuration
>            Reporter: Ryan Barnett
>            Assignee: Breno Silva Pinto
>             Fix For: 2.7.0
>
>
> Oftentimes there are different apps hosts (or proxies to) from apache. In order to minimize impedance mismatch issues, we need to be able to define multiple directive specifications (such as SecArgumentSeparator, SecCookieFormat, SecServerSignature) that can only be specified once in the Main configuration.
> These should be able to be specified within other Apache scope locations such a vhost, directory and location containers.

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