#767 send filter in body instead of URL #771
Open
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
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.
Let's continue our discussion here.
I noticed that OkHttp client does not support bodies in GET requests. It only works with Apache's HTTP client, using a custom request type.
Bodies in GET requests are not that common nowadays. In fact, it was discouraged in the deprecated RFC 2616. The new RFCs 7230-7237 for HTTP protocol do not contain this limitation any more. However, some legacy implementations do not support it and do not plan to support it in future versions. OkHttp client is one of them, see square/okhttp#3154