- From: Josh Cohen <joshco@gmail.com>
- Date: Sat, 3 Aug 2024 10:33:19 -0400
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: ietf-http-wg@w3.org
Received on Saturday, 3 August 2024 14:33:35 UTC
Thanks, I was just pondering potential ways to deal with middle boxes or other infrastructure by detecting their support. On Sat, Aug 3, 2024 at 3:45 AM Julian Reschke <julian.reschke@gmx.de> wrote: > On 02.08.2024 21:44, Josh Cohen wrote: > > 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 > > <https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1> > > There's no problem introducing new methods. The method registry is > completely orthogonal to the HTTP version. > > Best regards, Julian > > > -- --- *Josh Co*hen
Received on Saturday, 3 August 2024 14:33:35 UTC