Fix HTTP 100 Continue parsing to accept optional reason phrase #9702
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.
Merged in Botocore: boto/botocore#3543
Fixes HTTP 100 Continue parsing to accept responses without reason phrases, as allowed by RFC9110. The
_is_100_continue_status()
method currently requires exactly 3 parts (HTTP/1.1 100 Continue
), which prevents botocore from recognizing valid HTTP 100 responses, causing the client to never see "100 Continue response seen". This breaks compatibility with legitimate HTTP servers that follow the current HTTP specification. The fix changeslen(parts) >= 3
tolen(parts) >= 2
to accept both formats (HTTP/1.1 100 Continue
orHTTP/1.1 100
) while maintaining backward compatibility with existing servers.