1. Current Location: Home >  Router Encyclopedia >  Looking back, I found that my blog already uses HTTP/3 and QUIC

Looking back, I found that my blog already uses HTTP/3 and QUIC

Comparison of TCP Recognition Quadruple Network Cut Disconnection and QUIC Recognition Connection ID Connection Migration Comparison, Four Websites Alt-SVC Announcement H3 Field Table

Last week, I was browsing the web on my phone. When I reached the entrance of my residential complex, the WiFi disconnected, automatically switched to the data, the page had no white screen, and the video continued playing. Two years ago, this one would have been a break, spinning for at least two or three seconds. When I got back, I used curl to flip through the headers of several sites and found the secret hidden in a single line of small text—even my own small blog with double-digit visits was already using it.

First, look at the evidence: respond to the route change bar in your head

curl typed his own blog, and in response, there was a line in his head:

alt-svc: quic=":443"; h3=":443"; h3-Q046=":443"; h3-Q043=":443"

This line of alt-svc, in plain language, is a note the server stuffs you with the response: "This time you still took the old TCP route. Next time, you can come directly to me via port 443's UDP, which is called h3, faster." The following MA = 86400 (some sites write MA = 3600) is the expiration date of the note. Expired notes are invalid, so you can pick up another one by following the old path.

I casually tested four brands, and the gap was bigger than I imagined

Does the of ? has , and the in a long . ,
current HTTP versionthe site have an h3 note
My small blogHTTP/2codes for both new and old versions are listed
list: cloudflare.comHTTP/2 Yes, h3=":443", shelf life is one day
Bilibili doesn't have HTTP/2
Baidu doesn't have HTTP/1.1, and HTTP/2 hasn't even been launched yet

Two details are worth mentioning. First, having a note doesn't mean you're already using it: the first visit still obediently uses TCP, the browser stores the note properly—caching web file cache, reusing it locally—only on the second try switching to UDP. Second, the old code name h3-Q046 on their own blog—QUIC—was drafted for five or six years before the official draft. RFC 9000 (QUIC itself) was only officially adopted in May 2021, and RFC 9114 (HTTP/3) joined in June 2022. During the draft period, each version had a code starting with Q, and the server note listed all the old and new protocols, so any browser could match the code. It looks chaotic, but it's actually because compatibility is handled with great care.

Three things that TCP

is disliked

HTTP/2 has already done the task of cramming dozens of streams into a single connection, so why do we have to start over? The root of the problem lies with TCP itself—three things.

First, blocking the front of the line. Dozens of HTTP/2 streams are squeezed into a TCP pipe, which only recognizes byte order: if the 1000th byte is lost, even if the 1001st byte arrives early, it must wait in the buffer for resupply. A dozen video clips, images, and interface data were all queued in the tubes; losing one bag would result in collective punishment. Before loading the video splits, I wrote an article a ten-minute video was cut into 64 pieces. Those 64 requests were all squeezed into a single tube, and dropping one packet could hold a string.

The second item is the layered handshake. When you go out to pick up a webpage, do one round of TCP handshakes three times, the TLS handshake of the HTTPS lock, and do another round of TLS handshakes. TLS 1.3 also requires a round of back-and-forth. Before the first request can go on, run two or three RTTs in vain. RTT is a round-trip delay, cross-province access takes 30 milliseconds one-way, and two or three round-trips mean nearly 200 milliseconds wasted burn, not counting packet loss and restarts.

The third problem is the most critical issue: it breaks as soon as you change the net. TCP relies on quadruple connections: your IP, your port, the other IP, and the other port. The phone switches from WiFi to data, the IP starts with 192.168 to become a public address assigned by the carrier, the quadruple is voided, the connection is invalidated, and the webpage is white-screened and reconnected. The phrase "cutting the net and breaking the thread" mentioned at the beginning treats this disease.

QUIC's strategy: use UDP local foundations to build your own building

The idea behind QUIC's full suite is simple: since TCP can't be used (all network intermediaries recognize it and can't be changed), just don't use it—use UDP grounding and rebuild reliability, encryption, and multiplexing upstairs. When discussing the differences between TCP and UDP, we mentioned that UDP forgets after sending and guarantees nothing. QUIC precisely valued this simplicity: UDP's port chimneys are thin, so intermediate devices don't mess with it, and you decide how to design.

For the three diseases of TCP, three doses of QUIC. Streams are not connected to each stream: each stream manages its own order. If the video segment is lost, only block the video stream. Images and interfaces are still removed, and the queue leader blockage is removed from the root. Handshake in One: Transport layer handshake and TLS handshake are combined into one. The first visit completes a full RTT, and the visited site can still be 0-RTT—the first request is to leave with the handshake and run as soon as it lands.

The best part is connection migration. QUIC doesn't use IP to identify people; each connection sends a Connection ID, recognizing IDs rather than addresses. The phone's WiFi data cut, the IP changed, but the Connection ID didn't change. The server saw it was still the same ID, so I continued using the connection. No page white, no video overload—that's how it works. Of course, don't mythologize: the speed of the wireless signal itself can't be controlled; the speed should still be calculated by bandwidth, negotiation, and actual measurement.

What does it have to do with the home network

?

First, pour cold water on the situation: in a scenario where your home fiber is as stable as an old dog, HTTP/3 and HTTP/2 feel similar, and their advantages only become apparent on different lines. The higher the packet loss rate, the more obvious the benefits of non-concurrent traffic — when the 2.4G band is overwhelmed by neighbors' routers, when the subway signal fluctuates, or when only one elevator bar remains, QUIC's packet loss resistance truly pays off. Scrolling through the web on my commute is more stable than before—it's not just my imagination.

There are also cases where the opposite happens. UDP is treated differently: some company and campus networks limit UDP traffic speeds or even shut them down. If browsers can't connect via QUIC, they quietly revert to TCP on their own, leaving users unaffected and just not enjoying the new protocol. If your home has protocol-based QoS rules, UDP is prioritized very low, and HTTP/3 might actually be a bit slower than HTTP/2—new technologies aren't always fast, so you have to expect that.

Let's clarify two easily confused matters. First, the router doesn't need to be configured at all: this is an application layer matter; the browser and server can negotiate among themselves, and the router's optical modem at home doesn't need to be changed at all. Second, don't confuse it with encrypting DNS—the two have similar thinking, both "sneaking in through the existing channel on port 443," but that article covers the small issue of DNS queries using 443 encryption, while this article discusses the entire web transmission route switched to a different path—two different matters.

Take three minutes to see if you're using

it

Press F12 in Chrome or Edge to switch to the Network panel, refresh the page, right-click the header of the request list, and check out the Protocol column. If the column shows h3, it is already running on HTTP/3; if it shows h2, it is still the old HTTP/2 route. If you want to see more details, type chrome://net-internals/#quic in the address bar to see the current status of all QUIC connections.

Command-line party handles it: curl -sI URL | grep -i alt-svc. If there is output, it means the server has sent a note; if there is no output, it hasn't opened yet. To be honest, on my own computer, this curl 7.88 didn't have HTTP/3 support when compiled, so it couldn't send QUIC requests—but the notes are enough. Whether the connection is open is another matter, but whether it's announced or not is obvious.

Don't rush to feel you're losing out if you can't see H3; all three situations are normal: First, the site isn't even open (most of the domestic sites are still stuck at HTTP/2 or even 1.1, and Baidu's response speed makes me anxious for it); second, it's your first visit and the note hasn't warmed up yet; third, your network environment has blocked UDP, your browser automatically downgraded and all features are missing, but the speed discount is gone.

What situations should be remembered

? about the issues ? else. in . . , it might be triggered by
What should you doyou encounter related to HTTP/3
Switching WiFi and data traffic, the web doesn't connect, just connecting and migrating, doing nothing
In weak network environments, web browsing is more stable than beforeIf the stream isn't connected, you can cashand do nothing
Seeing h3 in DevTools, I thought it was an error and it was a protocol name, not an error code. Just recognize it
If the company website is having trouble at homeUDP, automatic downgrade, etc., or switching networks

The order is just a few steps: if you know there's a new path, open the protocol column to take a look, and don't be anxious if you see h3 or not. As for slow web page loading, check DNS, check cache, check cache, and if large files get disconnected, the next step is the honest Range mechanism. Breakpoint Resume article mentioned it—no matter how new the transmission protocol is, it can't withstand a fast-breaking network cable.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《Looking back, I found that my blog already uses HTTP/3 and QUIC》
Article URL: https://www.shunot.com/en/lybk/1162.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow