Improvements for content-length handling and chunked encoding#16
Merged
Conversation
szeka9
commented
Jun 9, 2026
szeka9
commented
Owner
- ignore content-length header when chunked encoding is set to improve compatibility with clients
- send chunked multipart responses to indicate response framing (due to lacking content-length header)
Ignore content length instead of rejecting requests containing both a content-length header and chunked transfer-encoding.
The content length is not available in advance when setting multipart response headers. Because of that, some clients hang after receiving multipart responses. Instead, use chunked encoding so that clients are aware of the response framing. Refactor multipart response generator and apply buffer-related error handling to multipart headers.
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.