Fix max_incomplete_event_size for complete oversized headers - #206
Open
Pitchfork-and-Torch wants to merge 1 commit into
Open
Pitchfork-and-Torch wants to merge 1 commit into
Pitchfork-and-Torch wants to merge 1 commit into
Conversation
Previously the size limit was only checked when next_event() returned NEED_DATA, so oversized request/response headers that arrived in a single chunk (or otherwise completed without an incomplete overflow) were accepted while the same bytes split across packets were rejected. Enforce the limit using bytes consumed by header events as well (python-hyper#182).
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
1 participant
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.
Summary
max_incomplete_event_sizewhen a complete header event is parsed, not only onNEED_DATA.Closes / relates to #182.
Test plan
pytest h11/tests/test_connection.py::test_max_incomplete_event_size_countermeasure