Re: [hybi] Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-01.txt

Andy Green <> Fri, 27 October 2017 07:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D7E0013F486 for <>; Fri, 27 Oct 2017 00:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 3.099
X-Spam-Level: ***
X-Spam-Status: No, score=3.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_SUMOF=5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ab9NLVUyizgT for <>; Fri, 27 Oct 2017 00:33:15 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 867BF139203 for <>; Fri, 27 Oct 2017 00:33:15 -0700 (PDT)
To: Amos Jeffries <>, John Fallows <>, Patrick McManus <>
Cc: hybi <>, HTTP Working Group <>
References: <> <> <> <> <>
From: Andy Green <>
Message-ID: <>
Date: Fri, 27 Oct 2017 15:32:05 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
In-Reply-To: <>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [hybi] Fwd: New Version Notification for draft-mcmanus-httpbis-h2-websockets-01.txt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Server-Initiated HTTP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Oct 2017 07:33:17 -0000

On 10/27/2017 02:59 PM, Amos Jeffries wrote:
> 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 

h2spec tests for these
 Malformed Requests and Responses
           ✔ 1: Sends a HEADERS frame with the "content-length" header 
field which does not equal the DATA frame payload length
           ✔ 2: Sends a HEADERS frame with the "content-length" header 
field which does not equal the sum of the multiple DATA frames payload 

> 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.

Well, that is banned in h2, but I guess you are right, if there is no 
content-length: it can just end on END_STREAM and there's no problem... 
it's my misunderstanding I guess.


> Amos