- From: Amos Jeffries <squid3@treenet.co.nz>
- Date: Fri, 27 Oct 2017 19:59:51 +1300
- To: Andy Green <andy@warmcat.com>, John Fallows <john.fallows@kaazing.com>, Patrick McManus <pmcmanus@mozilla.com>
- Cc: hybi <hybi@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
On 27/10/17 12:40, Andy Green wrote:> > The spec still needs to touch on the changes it is making to h2 DATA > frames, it assumes it is inheriting generic bidirectional transport from > h2, but it isn't. H2 DATA kills the stream if it comes outside of > whatever was told for content-length: on both sides, and eg h2spec > requires you to enforce that. So the spec requires changes in DATA > handling implementation for upgraded streams and should note it. AIUI, Content-Length remains optional in h2 as it was in 1.x. The h2 equivalent of Transfer-Encoding:chunked is being used by wss. Just a stream of DATA frames in both directions terminated by the END_STREAM flag instead of a specific Content-Length value. Amos
Received on Friday, 27 October 2017 07:00:21 UTC