Skip to content

http1connection: Stricter handling of transfer-encoding and whitespace - #3387

Merged
bdarnell merged 2 commits into
tornadoweb:masterfrom
bdarnell:chunked-parsing
Jun 6, 2024
Merged

bdarnell merged 2 commits into
tornadoweb:masterfrom
bdarnell:chunked-parsing

Conversation

@bdarnell

@bdarnell bdarnell commented Jun 6, 2024

Copy link
Copy Markdown
Member

Unexpected transfer-encoding values were previously ignored and treated
as the HTTP/1.0 default of read-until-close. This can lead to framing
issues with certain proxies. We now treat any unexpected value as an
error.

The RFC specifies that only tabs and spaces should be stripped.
Removing additonal whitespace characters can lead to framing
errors with certain proxies.

bdarnell added 2 commits June 5, 2024 16:50
Unexpected transfer-encoding values were previously ignored and treated
as the HTTP/1.0 default of read-until-close. This can lead to framing
issues with certain proxies. We now treat any unexpected value as an
error.
The RFC specifies that only tabs and spaces should be stripped.
Removing additonal whitespace characters can lead to framing
errors with certain proxies.
@bdarnell
bdarnell merged commit d65f6e7 into tornadoweb:master Jun 6, 2024
@bdarnell
bdarnell deleted the chunked-parsing branch June 6, 2024 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant