RFC 10008: The HTTP QUERY Method
11 points by Aks
11 points by Aks
see also: https://lobste.rs/s/mneqgx/rfc_10008_http_query_method
(for a second I was thinking it's the same sith different UI because title is the same)
In a hypothetical future where QUERY has universal support in infrastructure and software, will there still be a reason to spring for GET?
I'd love to have something like QUERY /animals with some filters in the body's json, but GET /animals/dog?format=something! The first one is usually GET + query params which can get lengthy and is limited IIRC and if you use GET + body you can put yourself in trouble, as I've seen proxies dropping silently body from such requests. POST doesn't cut it, as you'd have to guess without docs whether it's query or new object creation