- From: Martin Thomson <martin.thomson@gmail.com>
- Date: Mon, 20 May 2013 10:05:40 -0700
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 19 May 2013 20:22, Mark Nottingham <mnot@mnot.net> wrote: > We've currently incorporated the magic as: > >> The client connection header is a sequence of 25 octets (in hex notation) >> >> 464f4f202a20485454502f322e300d0a0d0a4241520d0a0d0a >> (the string FOO * HTTP/2.0\r\n\r\nBAR\r\n\r\n) followed by a SETTINGS frame (Section 3.8.4). > > That string was based upon the quick testing I did a while back. > > I'm curious to know how people feel about this; while it's cosmetic, do we want to do something a little more... expected, like: > > START * HTTP/2.0\r\n\r\nGO\r\n\r\n I don't care. Existence > colour for this particular bike shed. But I do know that 5 characters isn't going to fly. I know at least one (major) implementation that only expects 3 or 4 characters before the space.
Received on Monday, 20 May 2013 17:06:11 UTC