- From: Loïc Hoguin <essen@ninenines.eu>
- Date: Thu, 26 Jan 2017 11:35:14 +0100
- To: Cory Benfield <cory@lukasa.co.uk>, HTTP Working Group <ietf-http-wg@w3.org>
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
Received on Thursday, 26 January 2017 10:35:50 UTC