Replace http.NoBody with oohttp.NoBody in adapter #50
Conversation
This file contains 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
|
Good thinking! |
danilakovtunn
added a commit
to danilakovtunn/oohttp
that referenced
this pull request
Feb 13, 2024
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.
http2actualContentLengthinh2_bundle.gocompares request body againstoohttp.NoBody, but not againsthttp.Body. This results for unknownreqBodyContentLengthof-1forreadTrackingBodywith underlyinghttp.NoBodythus leading to a weird frames pattern, i.e. on the screenshot below a DATA frame is sent after a absent-bodied GET-request HEADER frameGiven
stdlibwrapper.gois an adaptor for standard http requests, I put the replacement there.