Content-Length, chunked transfer encoding and Host header improvements #2563
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.
Some fixes and improvements based on recent Discord discussions:
Host
header set, it is not going to be overwritten based on the request urlBody
types. If the content length is set, we will not use chunked transfer encoding, regardless of the body is streaming or not.Body
andHandler
constructors are duplicated now having a variant that gets a known content length, and one that does not (using the post-fixChunked
for them)