This repository has been archived by the owner on Nov 26, 2022. It is now read-only.
Use cleaner approach to include ModSecurity config #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our quest to enhance maintenability we've identified that extending the Apache configuration is not as straight-forward as it could be.
These changes:
conf/httpd.conf
conf/extra/httpd-modsecurity.conf
file that houses all the necessary configuration just for ModSecurity in a single locationI'm still not 100% happy with:
Include /etc/modsecurity.d/include.conf
statement (this was probably added for technical reasons, to make the include outside of the Apacheconf
folder work)/etc/modsecurity.d/include.conf
as such (it should probably convey "use me to include the ModSecurity configuration from Apache", but the pattern of "include" is broken here)Improvement suggestions welcome!