- From: David Krauss <potswa@gmail.com>
- Date: Tue, 1 Jul 2014 12:26:22 +0800
- To: Mark Nottingham <mnot@mnot.net>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 2014�07�01, at 11:29 AM, Mark Nottingham <mnot@mnot.net> wrote: > <https://github.com/http2/http2-spec/issues/536> > > It looks like the options so far are: > > 1) Define a registry for :headers > > 2) Make the list of acceptable :headers static with respect to the ALPN token > > Thoughts? Other options? Reserve them to HTTP/2 alone. The ALPN sets are going to leak into the regular namespace, and vice versa. Whether or not a particular header is pseudo will be just one more point of confusion. It would be nice if headers used for routing were segregated from others. This is already a distinguishing feature of the existing pseudo-headers. This doesn�t really dictate how extension should be accomplished, but more regulatory control over validity would help maximize the semantic value of the distinction between pseudo and normal.
Received on Tuesday, 1 July 2014 04:27:02 UTC