Whats going on Quic - HTTP3 ?

QUIC is commonly used network protocol on Google Services and also is next http protocol.

Last day I make a tests on Quic version 27. My test suite is very basic, client is Google Chrome Canary on Windows 10 and server side is Cloudflare.

I want to make a test with Quic because I am planning to use Quic on my software or solutions.

To enabling Quic on Google Chrome Canary you have to add --enable-quic --quic-version=h3-27 arguments on your Google Chrome Canary shortcut end of the target.

Connecting website with Quic now like a starting old engine motor. I try many times to establish with Quic but most of the time browser prefer http2 instead of http3. Open developer tools on Chrome and disable cache, refresh page and enable cache and again refresh page and again refresh, open Incognito mode on chrome. I do many times and finally, I get a HTTP3 connection on browser. Another analogy it’s like try to fire wet wood.

Also I unable to establish Quic-IETF behind NAT444 (CGN - Carrier Grade NAT or LSN Large Scale NAT) but I am very well access on Google Quic.
So I connect my PC to directly to ISP (Layer 2) to reduce NAT and it is work.

It means HTTP3 is not work in most of the Turkey. Because Turkish telecom operators doesn’t provide IPv6 and some local telecom organizations thinks that ‘IPv6 is not possible to use because most Services uses IPv4 and its not accessible at IPv6’. 🤔 DS-Lite 464XLAT ?.

Anyway I make test on IPv6 (It is not native IPv6. Ipv6 tunnel over Openvpn and Openvpn over another special tunnel mechanism) because I do not think use my Services only in Turkey and I don’t see any problem based on IPv6.

Here is a result. quic-on-chrome

You can see in picture used protocol says that, now I am using h3-27 (http3 draft 27).

Lets Take a Speed Test over Quic


Result is not impressive, except HTTP latency. Latency is like a ping command on terminal. While taking screen shot, the speed test is ended but if you look closer to network usage on task manager, Chrome still uses some bandwidth.
It might be order of some packets is changed due to latency or un stabile protocol and packets still transfers to browser. It’s bad.

End of the conclusion I guess, http3 is not stabile to use some project with some connection issues.

While writing this blog, I lost Internet connection. Turk Telekom Local SSG (which means provides Layer 2 connection between Turk Telekom local xDSL or Gpon network to ISPs) is not responds PPPOE packets.

© 2024 All rights reserved.

Powered by Hydejack v7.5.0