How to get Chrome to switch to HTTP3 on my site

Forum Moderators: phranque

Message Too Old, No Replies

How to get Chrome to switch to HTTP3 on my site

elos42

9:19 am on Oct 26, 2019 (gmt 0)

I can see that Chrome automatically switches to HTTP3 on google properties without any intervention required at the user level.
Is there anything I can do to get it to exhibit the same behavior on my website (which is http3-enabled thanks to Cloudflare)?
Or is this a feature that has been reserved by Google for its own sites, and can never be tapped by rival websites?

Please note the words 'automatically' and 'without any user intervention'

lammert

9:31 am on Oct 26, 2019 (gmt 0)

You have to switch on HTTP/3 support in your Cloudflare dashboard. More information can be found here on the Cloudflare blog [blog.cloudflare.com] You should navigate to the How do I enable HTTP/3 for my domain? paragraph for detailed instructions.

JorgeV

10:54 am on Oct 26, 2019 (gmt 0)

Hello-

As I was writing at the other topic, Google's sites are not HTTP/3, they are HTTP/2+QUIC 46. At least this is what I observe with my latest Chrome's version.

If I don't make mistake, if you use the LiteSpeed Web Server, you can serve HTTP/2+QUIC files.

elos42

1:38 pm on Oct 26, 2019 (gmt 0)

HTTP3 is already turned on for my website via Cloudflare dash. Yet Chrome doesn't use it. I guess the reason may be that it's not quic, but Http3. Probably I have to wait for the browser makers to implement it.

PS: It works on Chrome Canary if I start the browser with the necessary command line options.

JorgeV

4:32 pm on Oct 28, 2019 (gmt 0)

Hello-

This is it. In Canary, you have a real HTTP/3 support, however, even in Canary this is still experimental, because HTTP/3 connections appear as "HTTP/2 + QUIC 99". This might be a way to wait until HTTP/3 definitive standard. (It still working draft).

Google's sites are identified as HTTP/2 + QUIC 46, this was the last draft (46) of the QUIC protocol, before it was renamed into HTTP/3, which setup a new numbering , so the actual draft is HTTP/3 Draft 23.

So , just to say, wait and see. It shouldn't be long , before HTTP/3 is ready for prime time.

elos42

2:09 pm on Oct 31, 2019 (gmt 0)

Thanks. I figured as much.