On Wed, Sep 03, 2014 at 12:36:12PM -0700, Martin Thomson wrote:
> I think that this might be more substantial, so I'm going to confirm
> my choices here before proceeding.
>
> On 31 August 2014 19:37, Roy T. Fielding <fielding@gbiv.com> wrote:
> > HTTP/2 allows header field names that are not valid header fields in
> > the Internet Message Syntax used by HTTP/1.1 and cannot be registered
> > as such with IANA. An intermediary that is attempting to translate an
> > HTTP/2 request or response containing such an invalid field name into
> > an HTTP/1.1 message ought to ...
>
> I'm currently thinking that the correct choice is to treat the request
> or response as malformed
> (Received on Thursday, 4 September 2014 06:37:32 UTC