Skip to content

Expanding directive scope locations #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
rcbarnett-zz opened this issue Oct 17, 2013 · 1 comment
Closed

Expanding directive scope locations #372

rcbarnett-zz opened this issue Oct 17, 2013 · 1 comment
Assignees
@zimmerle

Comments

@rcbarnett-zz
Copy link
Contributor

MODSEC-218: 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.
@ghost ghost assigned zimmerle Oct 17, 2013
@rcbarnett-zz
Copy link
Contributor Author

Original reporter: rbarnett

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimmerle zimmerle

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zimmerle @rcbarnett-zz