feat: add example for content-type rule exclusion#286
Merged
fzipi merged 2 commits intocoreruleset:mainfrom May 1, 2026
Merged
Conversation
Member
Author
Signed-off-by: Felipe Zipitria <felipe.zipitria@owasp.org>
Member
|
I think you pushed your version of the theme/hugo-relearn that was older that the one upstream. Remember we are using submodules :) |
fzipi
approved these changes
May 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
There isn't any examples in the documentation on how to safely allow additional Content Types without opening up a complete request body bypass. ModSecurity/Coraza relies on the Content Type header in order to parse a request body, and most users will either blindly disable the rule or add the forbidden content type to the list of allowed Content Types without fully understanding the impact.
Further comments