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
The HTTP spec says that GET and DELETE requests don't have bodies, but sometimes you gotta.
Also, elastic search does a lot of GET body requests for large search requests (search is the most obvious use case for GET bodies).
Right now get takes a body object, but it just converts it to a query string and appends to the path. That functionality should either be removed or amended to add that to the body conditionally.
The text was updated successfully, but these errors were encountered:
Technically the spec allows for GET requests to have bodies and even clarified in 2014 by removing their message-body SHOULD be ignored (https://stackoverflow.com/a/983458), fetch throws a TypeError when you attempt to do this, and the maintainers seem to disagree with that spec (whatwg/fetch#551) so I don't see this happening in the foreseeable future.
Is there any more clarification on this issue? The HTTP protocol explicitly mentions that GET requests can have a body; is that impossible by using fetch? 🤯
The HTTP spec says that GET and DELETE requests don't have bodies, but sometimes you gotta.
Also, elastic search does a lot of GET body requests for large search requests (search is the most obvious use case for GET bodies).
Right now get takes a body object, but it just converts it to a query string and appends to the path. That functionality should either be removed or amended to add that to the body conditionally.
The text was updated successfully, but these errors were encountered: