[Mod-security-developers] [JIRA] Resolved: (MODSEC-216) Update the RESOURCE collection to use SecWebAppId Name Space

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

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

Breno Silva Pinto resolved MODSEC-216.
--------------------------------------

    Resolution: Fixed

> Update the RESOURCE collection to use SecWebAppId Name Space
> ------------------------------------------------------------
>
>                 Key: MODSEC-216
>                 URL: https://www.modsecurity.org/tracker/browse/MODSEC-216
>             Project: ModSecurity
>          Issue Type: Improvement
>      Security Level: Normal
>          Components: Rules
>            Reporter: Ryan Barnett
>            Assignee: Breno Silva Pinto
>             Fix For: 2.7.0
>
>
> The RESOURCE collection should be able to use the name space specified by SecWebAppId in the same way that the SESSION and USERID collections do.  This is needed so that URLs with the same name but are on different virtual hosts are not confused.  If no SecWebAppId is defined, then a resource collection should be -
> default_RESOURCE.dir 
> default_RESOURCE.pag
> If a SecWebAppId directive is used, Example -
> <VirtualHost www.foo.com> 
> SecWebAppId foo
> </VirtualHost>
> <VirtualHost www.bar.com> 
> SecWebAppId bar
> </VirtualHost>
> Then the persistent storage names should be:
> foo_RESOURCE.dir 
> foo_RESOURCE.pag
> bar_RESOURCE.dir 
> bar_RESOURCE.pag

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