[quicwg/base-drafts] Robert Wilton's HTTP/3 Comment 1 (#4804)

Lucas Pardue <notifications@github.com> Thu, 21 January 2021 14:32 UTC

Date: Thu, 21 Jan 2021 06:32:32 -0800
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZTWX6X5PGALQKUZPF6CVYYBEVBNHHC6KAOQA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4804@github.com>
Subject: [quicwg/base-drafts] Robert Wilton's HTTP/3 Comment 1 (#4804)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_60099080d6392_4a1a0413188d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/UoJVjpzYWrO23b0pTBuYkpze3fM>

@rgwilton said

> 4.1.1.  Field Formatting and Compression
>
> >   As in previous versions of HTTP, field names are strings containing a
> >   subset of ASCII characters that are compared in a case-insensitive
> >   fashion.  Properties of HTTP field names and values are discussed in
> >   more detail in Section 5.1 of [SEMANTICS].  As in HTTP/2, characters
> >   in field names MUST be converted to lowercase prior to their
> >   encoding.  A request or response containing uppercase characters in
> >   field names MUST be treated as malformed (Section 4.1.3).
>
> Why make the comparison case-insensitive given that the request MUST only use
> lowercase characters?  Presumably implementations will just do a regular case
> sensitive comparison?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4804

[quicwg/base-drafts] Robert Wilton's HTTP/3 Comme… Lucas Pardue
Re: [quicwg/base-drafts] Robert Wilton's HTTP/3 C… Martin Thomson
Re: [quicwg/base-drafts] Robert Wilton's HTTP/3 C… Mike Bishop
Re: [quicwg/base-drafts] Robert Wilton's HTTP/3 C… Mike Bishop