feat: add support for enforce_bodyproc_urlencoded config option#151
Merged
EsadCetiner merged 4 commits intoMay 17, 2026
Merged
Conversation
azurit
approved these changes
May 17, 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
2 participants
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.
This PR adds support for users enabling the
enforce_bodyproc_urlencodedoption which closes a possible bypass of CRS by making sure a body parser is always activated.There are a few cases where this behavior isn't desirable, this PR disables that config option in cases where it's not desirable.
I haven't updated the readme yet to avoid confusing existing users, I'll update it on the next release on the plugin.
I've been testing this for a few months so this should work fine.