Fix #6917: Correct Content-Length for io.StringIO with multi-byte UTF-8 #6955
+26
−1
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.
Fixes #6917
This PR resolves the incorrect
Content-Length
calculation when usingio.StringIO
as the request body. Key changes:io.StringIO
in thesuper_len
functionTest results:
Content-Length
now accurately reflects byte count forio.StringIO
with multi-byte characters