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

Re: Standard for upgrading based on URL?

From: Ben Schwartz <bemasc@google.com>
Date: Tue, 12 Oct 2021 16:05:34 -0400
Message-ID: <CAHbrMsAhLHc-_igCJeDYRavfcw39G3vNxbGqa-Nfe4wEOVFCBw@mail.gmail.com>
To: Felipe Gasper <felipe@felipegasper.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Clients generally upgrade to HTTP/2 automatically based on the ALPN process
in the TLS handshake.  Do you mean HTTP/3?

On Tue, Oct 12, 2021 at 1:30 PM Felipe Gasper <felipe@felipegasper.com>
wrote:

> Hello,
>
>         Is there any way, per currently-published standards, to upgrade a
> TLS connection from HTTP/1 to H2 based on its URL? e.g.:
>
> https://example.com/http1   <-- served via HTTP/1
>
> https://example.com/http2   <-- served via HTTP/3
>
>         This is possible with non-TLS via normal HTTP upgrades but doesn’t
> appear to be possible via the ALPN approach mandated for TLS-secured HTTP/2
> connections. It seems strange that there would be no way to do over TLS
> what’s easy to do in plain text. What am I missing?
>
>         Thank you!
>
> -FG
>

Received on Tuesday, 12 October 2021 20:05:59 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 12 October 2021 20:06:00 UTC