Repository navigation
Update dependency h2 to v4.4.1 - #7
Open
mend-for-github-com[bot] wants to merge 1 commit into
Open
mend-for-github-com[bot] wants to merge 1 commit into
mend-for-github-com[bot] wants to merge 1 commit into
Conversation
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.
This PR contains the following updates:
==4.1.0→==4.4.1By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
python-hyper/h2 (h2)
v4.4.1Compare Source
Bugfixes
v4.4.0Compare Source
API Changes (Backward Incompatible)
Stream.end_stream()now raisesNoSuchStreamErrororStreamClosedErrorexceptions, instead of a genericKeyError.content-lengthheaders with different values now raiseProtocolError.Previously, the first
content-lengthheader was accepted and later conflicting values were ignored. Thanks to Harshal Parekh for the report.content-lengthheaders according to RFC9110 grammar for numbers (1*DIGIT). Thanks to Arkadiusz Marta for the report.dataclass, which introduces new constructors with required arguments.Instantiating these events without arguments, as previously commonly used API pattern, will no longer work.
API Changes (Backward Compatible)
H2Connection.receive_datanow accepts any byte-like object thatimplements the buffer protocol, such as
bytes,bytearray, andmemoryview. Existingbytescallers are unaffected.Ordinary CONNECT now requires
:method=CONNECTand:authority, andforbids
:scheme/:path. Extended CONNECT (e.g., WebSocket) requires:scheme,:path,:authorityplus:protocol. (PR #1309)cookieand:method.Bugfixes
SETTINGS_ENABLE_PUSHvalues received from servers.v4.3.0Compare Source
API Changes (Backward Incompatible)
The main Python API is compatible, but some previously valid requests/response headers might now be blocked.
Use the
validate_inbound_headersconfig option if needed.Thanks to Sebastiano Sartor (sebsrt) for the report.
dataclass, which introduces new constructors with required arguments.Instantiating these events without arguments, as previously commonly used API pattern, will no longer work.
API Changes (Backward Compatible)
stream_idis guaranteed to not beNonefor most events now.This simplifies downstream type checking.
Bugfixes
v4.2.0Compare Source
API Changes (Backward Incompatible)
max_inbound_frame_sizeattribute onH2Stream.API Changes (Backward Compatible)
Bugfixes