You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the logic at [0], the request body handling will be ignored for all the requests with GET method currently, however some servers are supporting this kind of API/request like Elasticsearch. I did some searches on this, HTTP/1.1 does not seem to explicitly forbid this (correct me if I miss anything), and it seems some people have the similar requirements as well. I consider this is kind of needs on unclear defined standard, but from the perspective of a generic RESTful client, do you think it's a cent we can get to open the limitation to allow downstream developer decides API design or usage, and resty supports that in anyway?
Your design approach does make sense. I agree adding an option to do that seems like a good way to go currently, and disable the behavior by default to keep backward-compatible.
Would you like to take a look on my patch on this idea?
Hello,
According to the logic at [0], the request body handling will be ignored for all the requests with GET method currently, however some servers are supporting this kind of API/request like Elasticsearch. I did some searches on this, HTTP/1.1 does not seem to explicitly forbid this (correct me if I miss anything), and it seems some people have the similar requirements as well. I consider this is kind of needs on unclear defined standard, but from the perspective of a generic RESTful client, do you think it's a cent we can get to open the limitation to allow downstream developer decides API design or usage, and resty supports that in anyway?
Thanks!
[0] https://github.com/go-resty/resty/blob/master/client.go#L855
The text was updated successfully, but these errors were encountered: