3 ms·
Yeah, query seems just GET with a body. No difference in protocol nor behavior
by jbverschoor 4mo ago
Yeah, query seems just GET with a body. No difference in protocol nor behavior
- ComodoHacker 4mo agoExcept compatibility. If you're using classic GET and it's enough for you, you aren't affected.
- 4gotunameagain 4mo agoWhat is compatible with a QUERY but not with a GET ?
- dotancohen 4mo agoIntermediate proxies, caches, CDNs, firewalls, and load balancers.
- 4gotunameagain 4mo agoThat is only in the case of GET with a body though.
- dotancohen 4mo agoYes. That is the issue under discussion, e.g. not "classic GET".
- gl-prod 4mo agoThe difference is the method. Query you're saying I can use body. GET you should never use body.
- locknitpicker 4mo ago> The difference is the method. Query you're saying I can use body. GET you should never use body. The biggest win is how intermediary boxes now have concrete guidance that a specific HTTP request is both safe, idempotent, and carries a request body. Up until now none of this existed, and at best developers could use unsafe methods to carry request bodies (see GraphQL and how it uses POST for queries)
- _flux 4mo agoThere is the Accept-Query header https://www.rfc-editor.org/info/rfc10008/#appendix-A.3 https://www.rfc-editor.org/info/rfc10008/#appendix-A.3 that tells you can use QUERY. That's a bit different.