HTTP QUERY: The New Method That Fixes a Decades-Old Problem
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
The HTTP QUERY method, now standardized as RFC 10008, solves a long-standing problem with fetching filtered data over HTTP. GET requests struggle with complex query parameters due to URL length limits, and sending a body with GET is poorly supported. Using POST for reads is a common workaround but carries wrong semantics, is not idempotent, and is not cached by default. QUERY acts as 'GET with a body': it is safe, idempotent, and cacheable (with cache keys derived from both URI and body), and accepts any content type in the request body. Ecosystem adoption across servers, frameworks, CDNs, and clients is still needed.
Table of contents
The Problem: Fetching Filtered DataWhy Not Just Send a Body with GET?The POST WorkaroundEnter QUERYComparison with GET and POSTWhat’s Next: AdoptionReferences703.9K Impressions10 Comments