Re: Binary HTTP [RFC 9292] header name behavior

I guess it comes down to what deployed implementations are doing in
production. Google's implementation currently downcases on both encode and
decode. If everyone does it on encode, we'd be happy to shift to rejecting
on decode to be more in line with RFC 9413.

David

On Tue, Aug 12, 2025 at 3:22 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Wed, Aug 13, 2025, at 06:25, Ricky Perez wrote:
> > Thank you for the context Martin! So just to clarify, should downcasing
> > happen at the encoding path, at the decoding path, or at both paths?
>
> Encoding.  The decoder would validate that the name was lowercase and
> reject.
>
> > I'm happy to assist with filing the erratum, though let me know if you
> > prefer I hold that off in favor of following some other process.
>
> I'm going to wait for others to weigh in.  I don't entirely trust my
> instincts on this one.
>
>