Update protocol spec: Clients and servers must not attempt to decompress zero-length HTTP content #92
Conversation
This file contains 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
…ess zero-length HTTP content
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
akshayjshah
approved these changes
Nov 1, 2023
|
Thank you, Timo! |
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.
An issue in Connect for Kotlin reports that a client errored on a response with a zero-length body and the header
Content-Encoding: gzip.While this should not be a common form, the
fetchimplementations in modern browsers accept it without error. For better interoperability, this updates the protocol specification to require clients and servers to accept this form: They must not attempt to decompress zero-length payloads.