W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2021

Re: More on allowed field characters

From: Martin Thomson <mt@lowentropy.net>
Date: Mon, 23 Aug 2021 16:20:29 +1000
Message-Id: <68a1d032-a592-4096-9d3c-f39f00fe4995@www.fastmail.com>
To: ietf-http-wg@w3.org
Hey Willy,

Take another look at the text I've added to https://github.com/httpwg/http2-spec/pull/936

It now goes:

* HPACK can carry anything.
* HTTP defines what is valid.
* Recipients can treat anything that is not valid as malformed (using our formal definition).
* This section includes additional validation requirements.
* <those additional requirements>

On Mon, Aug 23, 2021, at 15:58, Willy Tarreau wrote:
> On Mon, Aug 23, 2021 at 03:53:08PM +1000, Martin Thomson wrote:
> > >   Even though HPACK is capable of carrying field names or values that
> > >   are not valid in HTTP, HTTP/2 implementations MUST NOT emit names
> > >   nor values that include characters disallowed by [HTTP].
> > 
> > That would be fine with me (s/emit/generate/), apart from it being somewhat
> > redundant with HTTP.
> 
> I know but when you see certain stuff like gRPC which try to be very
> intimate with H2 without real consideration for upper layers, you figure
> that if H2 is considered as convenient for some uses, it makes sense to
> remind certain important points that can definitely cause interoperability
> issues.
> 
> Cheers,
> Willy
> 
> 
Received on Monday, 23 August 2021 06:21:15 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 August 2021 06:21:16 UTC