- From: Cory Benfield <cory@lukasa.co.uk>
- Date: Thu, 17 Aug 2023 15:13:19 +0100
- To: Ryan Hamilton <rch@google.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
It's a good catch that RFC 9113 doesn't explicitly call out what you should do here. The response code should not be propagated to the next hop: as RFC 9113 says, you are not permitted to send a 101 in HTTP/2. This is a stream error of type PROTOCOL_ERROR. Cory On Wed, 16 Aug 2023 at 21:32, Ryan Hamilton <rch@google.com> wrote: > > Howdy Folks, > > The "101 Switching Protocols" upgrade mechanism is not supported in HTTP/2 or HTTP/3 according to RFC 9113: > > HTTP/2 does not support the 101 (Switching Protocols) informational status code (Section 15.2.2 of [HTTP]). > > > and RFC 9114: > > HTTP/3 does not support the HTTP Upgrade mechanism (Section 7.8 of [HTTP]) or the 101 (Switching Protocols) informational status code (Section 15.2.2 of [HTTP]). > > > However, it wasn't immediately clear to me what an endpoint should do if it receives such a response code. I'm guessing this should be considered a stream error, but maybe there is an argument that this response code should be propagated to the next hop. Thoughts? > > Cheers, > > Ryan
Received on Thursday, 17 August 2023 14:13:37 UTC