The New HTTP QUERY Method Every REST API Should Use (RFC 10008)

REST has always had a weak spot: complex queries. GET can’t carry enough data in a URL, so most teams fake it with POST — and lose caching, safe retries, and idempotency in the process. HTTP just got a fix: a new verb called QUERY.

This video reacts to a LinkedIn post by Martin Forstner, lead software architect at Zühlke, on the newly published RFC 10008.

In this video:

  • Why REST’s query strings hit a wall with complex, multi-entity filters
  • Why using POST for reads breaks caching, retries, and idempotency
  • What the new QUERY method actually does differently
  • GET vs. POST vs. QUERY, side by side
  • How QUERY requests and the Accept-Query header work in practice
  • Where adoption stands today (Spring already has an open PR)

QUERY won’t land in your stack tomorrow, but it closes one of REST’s oldest design gaps.

Recommended products

Subscribe to channel

More from the Blog


0
    0
    Your Cart
    Your cart is empty
      Apply Coupon
      Scroll to Top