- From: Ben Schwartz <bemasc@google.com>
- Date: Wed, 18 Jan 2023 11:21:06 -0500
- To: Momoka Yamamoto <momoka.my6@gmail.com>
- Cc: ietf-http-wg@w3.org
- Message-ID: <CAHbrMsDSFRHQhciZM6PYNL=qoWAK8N-g+Pd39NngBKxag62wpA@mail.gmail.com>
This draft says Suppose the server supports extended CONNECT but not bootstrapping > WebSockets over that HTTP connection. In this case, the client sending a > WebSocket handshake request will result in a response of 501 (Not > Implemented) status code (Section 15.6.2 of [HTTP]), and the client would > need to fall back to trying the WebSocket handshake over HTTP/1. I don't think this is correct. If the client encountered this error code, it would just fail the WebSocket setup attempt. In general, I don't think we should be asking clients to retry requests across different HTTP versions. If you publish wss:// URIs for your domain, you need to support WebSocket on all the domain's HTTP versions. On Wed, Jan 18, 2023 at 10:45 AM Momoka Yamamoto <momoka.my6@gmail.com> wrote: > > Hello, > > I have submitted an internet-draft proposing a SETTINGS_ENABLE_WEBSOCKETS > settings parameter. > With WebSockets not being the only protocol that uses extended CONNECT ( > https://github.com/ietf-wg-webtrans/draft-ietf-webtrans-http3/issues/68#issuecomment-1310323592 > ), > Before starting the WebSocket handshake, it will be nice to know if the > server supports bootstrapping WebSockets over HTTP/2 or HTTP/3. > > I would love to know your thoughts > > Momoka Y > > ---------- Forwarded message --------- > From: <internet-drafts@ietf.org> > Date: Sat, Jan 7, 2023 at 6:30 PM > Subject: New Version Notification for > draft-momoka-httpbis-settings-enable-websockets-00.txt > To: Momoka Yamamoto <momoka.my6@gmail.com> > > > > A new version of I-D, > draft-momoka-httpbis-settings-enable-websockets-00.txt > has been successfully submitted by Momoka Yamamoto and posted to the > IETF repository. > > Name: draft-momoka-httpbis-settings-enable-websockets > Revision: 00 > Title: SETTINGS_ENABLE_WEBSOCKETS settings parameter for HTTP/2 > and HTTP/3 > Document date: 2023-01-07 > Group: Individual Submission > Pages: 5 > URL: > https://www.ietf.org/archive/id/draft-momoka-httpbis-settings-enable-websockets-00.txt > Status: > https://datatracker.ietf.org/doc/draft-momoka-httpbis-settings-enable-websockets/ > Html: > https://www.ietf.org/archive/id/draft-momoka-httpbis-settings-enable-websockets-00.html > Htmlized: > https://datatracker.ietf.org/doc/html/draft-momoka-httpbis-settings-enable-websockets > > > Abstract: > This document proposes a new HTTP settings parameter, > SETTINGS_ENABLE_WEBSOCKETS. This parameter indicates whether the > server supports bootstrapping WebSockets over the established > connection. > > > > > The IETF Secretariat > > >
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Wednesday, 18 January 2023 16:21:33 UTC