W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2022

Re: RFC 9113 and :authority header field

From: Stefan Eissing <stefan@eissing.org>
Date: Thu, 30 Jun 2022 16:50:48 +0200
Cc: "tatsuhiro.t@gmail.com" <tatsuhiro.t@gmail.com>, HTTP <ietf-http-wg@w3.org>
Message-Id: <392D0C8A-4EBC-4DD9-8C84-F06E837177BC@eissing.org>
To: Willy Tarreau <w@1wt.eu>

> Am 30.06.2022 um 09:13 schrieb Willy Tarreau <w@1wt.eu>:
> No, this one should not forge a :authority where there was not any,
> it's the case that's covered by the "unless" rule in the spec, so
> you'd get this:
> H1 GET / HTTP/1.1, Host: example.com
> -> H2 host: example.com, :scheme: <context>
> -> H0 GET / HTTP/1.0, Host: example.com
> -> H1 GET / HTTP/1.1, Host: example.com

I see. That is what you described as an "internal flag" to preserve that information in a gateway. And what is causing the problems at some CDNs (missing :authority). Thanks.

Well, since Apache httpd misses that flag our http2 proxy always sends :authority. I think I'll leave it that way until there is more acceptance of such a change.

Kind Regards,
Received on Thursday, 30 June 2022 14:51:07 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:07 UTC