Fix bytes/string issue when using chunked transfer encoding#194
Open
mstojcevich wants to merge 1 commit intofiorix:masterfrom
Open
Fix bytes/string issue when using chunked transfer encoding#194mstojcevich wants to merge 1 commit intofiorix:masterfrom
mstojcevich wants to merge 1 commit intofiorix:masterfrom
Conversation
…for HTTP 1.1 requests)
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
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.
When chunked transfer encoding is used (the default behavior for responses to HTTP 1.1 requests) an exception gets raised because
transform_chunkreturns an str, which then gets appended toheadersinflush, which is a bytestring, so you get a traceback like this:There was also another bug where
ChunkedTransferEncoding.transform_chunkwould includeb'prefixes on the chunk size and chunk contents.