Allow GET requests to have a request body #8306
Closed
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
* As per [RFC 9110 - HTTP Semantics - section 9.3.1. GET](https://datatracker.ietf.org/doc/html/rfc9110#section-9.3.1): ``` (...) A client SHOULD NOT generate content in a GET request unless it is made directly to an origin server that has previously indicated, in or out of band, that such a request has a purpose and will be adequately supported. ```
|
Prior discussion in #3154 |
|
Isn't desirable for OkHttp to be compliant with RFC 9110 - HTTP Semantics? Or is it just technically not possible? Is there any workaround besides using a non-compliant method? |
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.
Although it is not recommended, if agreed between client and server, GET requests may have content.
(...) A client SHOULD NOT generate content in a GET request unless it
is made directly to an origin server that has previously indicated,
in or out of band, that such a request has a purpose and will be
adequately supported. (...)
( != must not)