- From: Alessandro Ghedini <alessandro@ghedini.me>
- Date: Tue, 3 Apr 2018 18:17:10 +0100
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, Patrick McManus <mcmanus@ducksong.com>
On Thu, Mar 29, 2018 at 08:48:28AM +1100, Mark Nottingham wrote: > Hi everyone, > > Patrick (as editor) has incorporated the discussion from London and believes this is ready for WGLC; there are no open issues. > > Please have a look at: > https://tools.ietf.org/html/draft-ietf-httpbis-h2-websockets-01 > > ... and bring up any issues on-list or on its issues list; likewise statements of support (or otherwise) for publication on-list would be appreciated. Hello, Need a clarification regarding section 5. It says: Implementations using this extended CONNECT to bootstrap WebSockets do not do the processing of the [RFC6455] Sec-WebSocket-Key and Sec- WebSocket-Accept headers as that functionality has been superseded by the :protocol pseudo-header. does that mean that a transparent proxy (say, a CDN, as opposed to a traditional HTTP CONNECT proxy) that proxies WS connections and speaks HTTP/2 with the client but HTTP/1 with the origin server, is expected to generate -Key and validate -Accept itself? Might be worth mentioning this in section 7 as well. Cheers
Received on Tuesday, 3 April 2018 17:17:45 UTC