RFC 10008: The HTTP Query Method
Comments on “RFC 10008: The HTTP Query Method”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
RFC 10008, a Standards Track document from the IETF, defines an HTTP QUERY method that carries query input in the request body while being explicitly safe and idempotent. That lets caches and clients retry or cache such requests, which POST-based queries do not allow, and avoids URI length limits and logging of sensitive parameters. Servers can return Location or Content-Location URIs for later GET requests, and an Accept-Query header advertises supported formats. IANA has registered both. Caches must key on request content, and browsers will send CORS preflights.
Why it ranked
No. 2 of 62 with a score of 0.72. The panel rated it highest on new information (0.95) and substantiated (0.89), lowest on significance (0.64). The judges disagreed most on reader interest (spread 0.43), so the story is marked contested.
- AI judgeJudge 2claude-haiku-5-5
- Finalized IETF standard adding QUERY HTTP method, a notable protocol change for API builders; primary spec text with thorough examples, though it is a standards document rather than a project.
- AI judgeJudge 3gpt-5.6-luna
- A primary Internet Standards Track specification introduces a cacheable, retryable HTTP method for request bodies too large or sensitive for GET. It is technically detailed and broadly relevant, though adoption and ecosystem impact remain uncertain.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.72total under rubric v2.3Contestedjudges differ by 0.43 on reader interest
- Significance0.64
- Reader interest0.72
- Audience breadth0.79
- Practical relevance0.72
- Substantiated0.89
- Technical depth0.87
- New information0.95
- Counts against: Promotional0.03
- Counts against: Overclaim0.10
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.58 | 0.60 | 0.75 | 0.64 | 0.17 | +0.24 | +0.155 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.47 | 0.80 | 0.90 | 0.72 | 0.43 , above the contested threshold | +0.26 | +0.188 |
| Audience breadthHow many people who build technology does it concern? | 0.76 | 0.80 | 0.80 | 0.79 | 0.04 | +0.13 | +0.102 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.61 | 0.70 | 0.85 | 0.72 | 0.23 | +0.22 | +0.159 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.78 | 0.90 | 1.00 | 0.89 | 0.22 | +0.05 | +0.045 |
| Technical depthHow technically substantive is it? | 0.96 | 0.80 | 0.85 | 0.87 | 0.16 | +0.05 | +0.044 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.95 | 0.99 | 0.95 | 0.08 | +0.05 | +0.048 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.02 | 0.00 | 0.03 | 0.06 | −0.19 | −0.005 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.16 | 0.10 | 0.03 | 0.10 | 0.13 | −0.11 | −0.011 |
| Sum of contributions | +0.724 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.724 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-15/2/"><img src="https://rubric.hrih.si/badge/2026-11-15/2.svg" alt="Ranked #2 on Rubric, 15 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 4 matches source · 3 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenVersion
RFC 10008 defines the HTTP QUERY method as safe and idempotent, so requests can be automatically repeated or restarted without concern for partial state changes.
The article gives no link or citation for it.
The article says “QUERY requests can be automatically repeated or restarted without concern for partial state changes”
The source says No source to compare with.
Matches sourceNumber
HTTP Semantics (RFC 9110, Section 4.1) recommends that senders and recipients support at least 8000 octets in URIs.
The cited source says the same thing.
The article says “note that Section 4.1 of [HTTP] recommends senders and recipients to support at least 8000 octets”
The source says “It is RECOMMENDED that all senders and recipients support, at a minimum, URIs with lengths of 8000 octets in protocol elements”
Source cited by the article: rfc-editor.org/rfc/rfc9110
Matches sourceDate
IANA has added the QUERY method to the HTTP Method Registry as safe and idempotent.
The cited source says the same thing.
The article says “IANA has added the QUERY method to the "Hypertext Transfer Protocol (HTTP) Method Registry”
The source says “QUERY | yes | yes | RFC 10008, Section 2”
Source cited by the article: iana.org/assignments/http-methods
Matches sourceVersion
IANA has added the Accept-Query field to the HTTP Field Name Registry.
The cited source says the same thing.
The article says “IANA has added the Accept-Query field to the "Hypertext Transfer Protocol (HTTP) Field Name Registry”
The source says “Accept-Query permanent List RFC 10008, Section 3: The HTTP QUERY Method”
Source cited by the article: iana.org/assignments/http-fields
Couldn’t checkNumber
The HTTP Method Registry already contains three other safe and idempotent methods: PROPFIND, REPORT and SEARCH.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “already contains three other methods with the properties "safe" and "idempotent": "PROPFIND" [RFC4918], "REPORT" [RFC3253], and "SEARCH" [RFC5323”
The source says No passage could be compared.
Source cited by the article: iana.org/assignments/http-methods
No source givenDate
The early stages of the QUERY specification used the method name SEARCH.
The article gives no link or citation for it.
The article says “Indeed, the early stages of this specification used "SEARCH”
The source says No source to compare with.
No source givenDate
Discussion on this HTTP method was reopened by Asbjørn Ulsberg during the HTTP Workshop in 2019.
The article gives no link or citation for it.
The article says “Discussion on this HTTP method was reopened by Asbjørn Ulsberg during the HTTP Workshop in 2019”
The source says No source to compare with.
Matches sourceCausal conclusion
QUERY requests from CORS-implementing user agents require a preflight request because QUERY is not a CORS-safelisted method.
The cited source says the same thing.
The article says “will require a "preflight" request, as QUERY does not belong to the set of CORS-safelisted methods”
The source says “A CORS-safelisted method is a method that is `GET`, `HEAD`, or `POST”
Source cited by the article: fetch.spec.whatwg.org
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:46 UTC. It played no part in the ranking.