From c1d3d97d212c6e6ba1c29905f38fa611c7269779 Mon Sep 17 00:00:00 2001 From: Andrew Godwin Date: Tue, 23 Mar 2021 15:44:15 -0600 Subject: [PATCH] Clarify response header capitalisation We don't actually REQUIRE lowercase, it's just a nice convention to have. Some rare clients do, actually, care about case, so carve out a best-effort channel for that. --- specs/www.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/specs/www.rst b/specs/www.rst index 99aa8cc5..88c1bbc9 100644 --- a/specs/www.rst +++ b/specs/www.rst @@ -104,7 +104,8 @@ The *connection scope* information passed in ``scope`` contains: ``value`` is the header value. Order of header values must be preserved from the original HTTP request; order of header names is not important. Duplicates are possible and must be preserved in the message as received. Header names - must be lowercased. Pseudo headers (present in HTTP/2 and HTTP/3) must be + should be lowercased, but it is not required; servers should preserve header case + on a best-effort basis. Pseudo headers (present in HTTP/2 and HTTP/3) must be removed; if ``:authority`` is present its value must be added to the start of the iterable with ``host`` as the header name or replace any existing host header already present.