- From: Willy Tarreau <w@1wt.eu>
- Date: Tue, 29 Aug 2017 09:04:38 +0200
- To: Piotr Sikora <piotrsikora@google.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>, Craig Tiller <ctiller@google.com>
On Mon, Aug 28, 2017 at 11:56:08PM -0700, Piotr Sikora wrote: > To reiterate, binary header field values prefixed with NUL byte (0x00) > would be sent only to binary-aware peers that announced support for > binary headers via HTTP/2 SETTINGS option, therefore, those headers > would never be seen by HTTP/1.x or HTTP/2 parsers that aren't aware of > this extension, so I'm not sure if there is any difference whether > it's <NUL>, <CR> or any combination of those. So if that's done only after the sender has received the recipient's SETTINGS frame, I think it's safe, possibly at the cost of an extra RTT, unless such behaviour could be enforced by configuration where that makes sense. Willy
Received on Tuesday, 29 August 2017 07:05:04 UTC