- From: Josh Cohen <joshco@gmail.com>
- Date: Fri, 2 Aug 2024 15:44:23 -0400
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Patrick Meenan <patmeenan@gmail.com>, cxres@protonmail.com, ietf-http-wg@w3.org
Received on Friday, 2 August 2024 19:44:39 UTC
Thanks for the clarification. Looking at the http2 rfc9113[1], bottom of section 8.3.1, says: "Individual HTTP/2 requests do not carry an explicit indicator of protocol version. All HTTP/2 requests implicitly have a protocol version of "2.0"" So, there's no longer an explicit version string, or header. The reason I asked was when considering new methods. The option of revving the version of the messaging/semantics layer isn't feasible. https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1 On Thu, Aug 1, 2024 at 10:14 AM Julian Reschke <julian.reschke@gmx.de> wrote: > Am 01.08.2024 um 16:11 schrieb Josh Cohen: > > Rahul, All, > > > > Rahul, I'm reading your draft. > > > > All, > > > > When using h2 & h3, when the client does a request, at the messaging > > layer, what is the request line version string? > > ... > > There is no "request line" in H2 and H3. > > Best regards, Julian > -- --- *Josh Co*hen
Received on Friday, 2 August 2024 19:44:39 UTC