fix request content-length header erasing after post redirect #391
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 performing a POST request with some data to server and it answers with redirect 303 See other with location of resource.
So when we are trying to handle redirect to that resource, we still have a Content-Length header left from POST. It cause
send_headers
method to try to write payload with no data but with lengthMaybe this fix just fixing the symptom, but what I want is to pay attention at POST with data redirect problem