Fix bytes/string issue when using chunked transfer encoding #194
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_chunk
returns an str, which then gets appended toheaders
inflush
, which is a bytestring, so you get a traceback like this:There was also another bug where
ChunkedTransferEncoding.transform_chunk
would includeb'
prefixes on the chunk size and chunk contents.