- From: Martin Thomson <mt@lowentropy.net>
- Date: Wed, 16 Sep 2026 07:57:01 +1000
- To: rfc-editor <rfc-editor@rfc-editor.org>, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>, "Francesca Palombini" <francesca.palombini@ericsson.com>, "Cory Benfield" <cbenfield@apple.com>, "Mark Nottingham" <mnot@mnot.net>, "Mike Bishop" <mbishop@evequefou.be>
- Cc: ietf-http-wg@w3.org, "Antun Jurkovic" <antunjurkovic@gmail.com>
Technically correct, which is the best kind of correct. Though I doubt anyone will struggle with comprehension, and the fix could even make comprehension harder ("what is this query thing you speak of, there is no `:query`?!?!1"), this might be good to hold for an update.
On Tue, Sep 15, 2026, at 23:11, rfc-editor@rfc-editor.org wrote:
> The following errata report has been submitted for RFC9113,
> "HTTP/2"
>
> --------------------------------------
> You may review the report below and at:
> https://errata.rfc-editor.org/eid9175/
>
> --------------------------------------
> Type: Technical
> Reported by: Antun Jurkovikj <antunjurkovic@gmail.com>
>
> Section 8.3.1 says:
>
> Original Text
> -------------
> - an OPTIONS request for an "http" or "https" URI that does not
> include a path component; these MUST include a ":path" pseudo-
> header field with a value of '*' (see Section 7.1 of [HTTP]).
>
> Corrected Text
> --------------
> - an OPTIONS request for an "http" or "https" URI that does not
> include a path or query component; these MUST include a
> ":path" pseudo-header field with a value of '*' (see
> Section 7.1 of [HTTP]).
>
> Notes
> -----
> The :path definition includes both the path and query components, but the
> OPTIONS exception tests only for an absent path. RFC 9112 Section 3.2.4
> limits the corresponding conversion to "*" to an empty path and no query
> component.
>
> For example, a valid HTTP/1.1 OPTIONS request to a proxy with absolute-form
> request-target https://example.com?x=1 has an empty path and a query. Its
> HTTP/2 :path is /?x=1, not *. A present but empty query likewise needs its
> delimiter preserved: https://example.com? maps to /?.
>
> Reading the exception as limited to server-wide OPTIONS gives the intended
> result, but that limitation is missing from its stated condition. This is
> an instruction conflict, not a claim that the combined HTTP rules permit
> query loss or that deployed implementations lose queries.
>
> Adding "or query" makes the condition explicit while preserving server-wide
> OPTIONS, ordinary path/query construction, and the other request mappings.
>
> RFC 9114 Section 4.3.1 contains the corresponding path-only OPTIONS condition.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> will log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC9113 (draft-ietf-httpbis-http2bis)
> --------------------------------------
> Title : HTTP/2
> Publication Date : June 2022
> Author(s) : M. Thomson, Ed., C. Benfield, Ed.
> Category : Proposed Standard
> Source : httpbis (wit)
> Stream : IETF
> Verifying Party : IESG
Received on Tuesday, 15 September 2026 21:57:25 UTC