[whatwg/url] Use in HTTP2/3 Pseudo-Headers (Issue #809)

### What is the issue with the URL Standard?

Apologies if this has been discussed before, but: I noticed that HTTP/3's definition of the `:path` pseudo-header (like the definition in HTTP/2) incorporates RFC 3986 by reference; I know that WHATWG URL and RFC 3986 diverge in places, so it struck me that this might cause some problems/ambiguities. Has this come up before and is it an issue?

Specifically, the H3 RFC [says that `:path`](https://datatracker.ietf.org/doc/html/rfc9114#section-4.3.1-2.14.1):

> Contains the path and query parts of the target URI (the "path-absolute" production and optionally a ? character (ASCII 0x3f) followed by the "query" production; see Sections [3.3](https://www.rfc-editor.org/rfc/rfc3986#section-3.3) and [3.4](https://www.rfc-editor.org/rfc/rfc3986#section-3.4) of [[URI](https://datatracker.ietf.org/doc/html/rfc3986)].

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/809
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/809@github.com>