Re: HTTP/2 plaintext upgrade

Loïc Hoguin <essen@ninenines.eu> Thu, 26 January 2017 10:38 UTC

Resent-Date: Thu, 26 Jan 2017 10:35:54 +0000
Resent-Message-Id: <E1cWhPG-0008Rz-2A@frink.w3.org>
To: Cory Benfield <cory@lukasa.co.uk>, HTTP Working Group <ietf-http-wg@w3.org>
References: <AC89F2FD-F183-4B17-B528-60821D2D4EB8@lukasa.co.uk>
From: Loïc Hoguin <essen@ninenines.eu>
Organization: Nine Nines
Message-ID: <111bbf48-dc11-9f8a-60b0-5f28810c318f@ninenines.eu>
Date: Thu, 26 Jan 2017 11:35:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version: 1.0
In-Reply-To: <AC89F2FD-F183-4B17-B528-60821D2D4EB8@lukasa.co.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Received-SPF: none client-ip=217.72.192.75; envelope-from=essen@ninenines.eu; helo=mout.kundenserver.de
Subject: Re: HTTP/2 plaintext upgrade
Archived-At: <http://www.w3.org/mid/111bbf48-dc11-9f8a-60b0-5f28810c318f@ninenines.eu>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Hello,

On 01/26/2017 11:13 AM, Cory Benfield wrote:
> I’ve got a question about HTTP/2 plaintext upgrade. RFC 7540 Section 3.2.1 says about the HTTP2-Settings header field:
>
>> The content of the HTTP2-Settings header field is the payload of a SETTINGS frame
>
> My initial implementation provided an entire SETTINGS frame in the HTTP2-Settings field, but a contributor has pointed out that the word “payload” may mean that only the body of the SETTINGS frame should be provided. It’s not really entirely clear to me in the text which I should do, and there are no textual examples either, so I’m genuinely not sure.
>
> Can I get an idea of what other implementers have done here?

I understood "payload" as the frame payload defined in section 4.1:

    All frames begin with a fixed 9-octet header followed by a variable-
    length payload.

     +-----------------------------------------------+
     |                 Length (24)                   |
     +---------------+---------------+---------------+
     |   Type (8)    |   Flags (8)   |
     +-+-------------+---------------+-------------------------------+
     |R|                 Stream Identifier (31)                      |
     +=+=============================================================+
     |                   Frame Payload (0...)                      ...
     +---------------------------------------------------------------+

I have however only used this with a client I implemented myself.

-- 
Loïc Hoguin
https://ninenines.eu

HTTP/2 plaintext upgrade Cory Benfield
Re: HTTP/2 plaintext upgrade Loïc Hoguin
Re: HTTP/2 plaintext upgrade Daniel Stenberg
Re: HTTP/2 plaintext upgrade Kazuho Oku