Back off desync_mitigation_mode to defensive #43
Merged
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.
Setting desync_mitigation_mode to strictest breaks clients that
aren't strictly RFC 7230 compliant (notably, AWS API Gateway).
Setting this attribute to defensive provides sufficent protection
against desync attacks, while still allowing requests from clients
that we can't perfect.
https://en.wikipedia.org/wiki/Robustness_principle