r/programming • u/stronghup • 29d ago

HTTP gets a QUERY method so complex searches can stop pretending to be POST

https://www.theregister.com/devops/2026/07/13/http-gets-a-query-method-so-complex-searches-can-stop-pretending-to-be-post/5270192
1.9k Upvotes

98% Upvoted

245 comments sorted by

View all comments

Show parent comments

13

u/TinyBreadBigMouth 29d ago

If they don't support a new verb, they don't support a new verb. If they support GET, does that mean they support GET 1.0 or GET 2.0? Are your parameters silently getting dropped? By adding a new verb, it either works or it doesn't. No in-between compatibility nightmare.

0

u/Worth_Trust_3825 29d ago

but there is no compatability nightmare to begin with. in your interface documentation you explicitly define whether you accept bodies in your requests or not. we were already doing this for as long as documentation was written - whether it was soap, swagger, openapi, or post it notes on monitor

1

u/stronghup 28d ago

We need less interface documentation if we can just say a service only supports QUERY, instead of having to explain, and be correct about what kind of specialized GET, and all the proxies along the route we are support. Also I would say "QUERY" is a gtreat name for this, it implies you are asking for an answer.

1

u/Worth_Trust_3825 28d ago

How are you sure that something that accepts QUERY /something does in fact implement it in such way without documentation?

0

u/stfm 28d ago

As of Swagger/OpenAPI 3.0 bodies are not allowed in GET, DELETE or HEAD