Show how to disable chunked transfer encoding in Go and Java server examples #13
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
Member
Author
|
Related to this: in #12 I implemented chunked transfer encoding in the Python server example |
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.
I was looking at the raw output from the different server examples by running
and examining
output.rawwith a hex viewer, and I noticed that the Go server example (using http) and the Java server example (using Jetty) both use chunked transfer encoding by default when theContent-Lengthheader is not set, whereas the Python server example (using http.server) and the Rust server example in #8 (which doesn't use any high-level HTTP framework) do not.I added comments in both examples showing how to disable chunked transfer encoding.