For Chrome users, this open source extension will tell you what protocol the browser is using for each website being accessed: https://chrome.google.com/webstore/detail/http-indicator/hgc...
[deleted]
The majority of Facebook's traffic now uses QUIC and HTTP/3
21–30 of 149 posts
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#22By the way, even though it is not yet turned on by default, http3 support is present in Firefox and can be activated by toggling 'network.http.http3.enabled' in about:config to true. I have had it enabled for a few weeks and everything seems okay except that rarely I've noticed a few sites not loading the first time I visit them but needing a 'refresh', but I'm not sure if this is because of the new QUIC code or just…
It likely is. I played around with the implementation earlier on (it's now > 6 weeks back), and it still had some issues. E.g. the quic connection would time out at the server without the browser knowing about it. And all follow-up requests silently failed. A page refresh helped that.
Another thing where a full page refresh helps is towards getting consistency on whether HTTP/3 is available or not, because the client might make another HTTP/2 request instead and refresh the Alt-Svc information.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#23Could that explain this : the new UI, appart from being terrible, is often seeing slowdowns for me ?
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#24Is this possible with NodeJS + express already? I didn't see any package for that or config
Node.js has builtin HttpV2 support but no v3 support IIRC. Which is not a deal breaker because any production app should already have a load balancer/proxy in front of it, which do have QUIC support.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#25By the way, even though it is not yet turned on by default, http3 support is present in Firefox and can be activated by toggling 'network.http.http3.enabled' in about:config to true. I have had it enabled for a few weeks and everything seems okay except that rarely I've noticed a few sites not loading the first time I visit them but needing a 'refresh', but I'm not sure if this is because of the new QUIC code or just…
Had constant problems loading Youtube. Finally someone on r/Firefox helped me solve it by seeing what in my config was different from default. This value was it and everything worked well after the setting was reverted and restarting.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#26Bit offtopic and dumb but..
> Facebook has a mature infrastructure that allows us to safely roll out changes to apps in a limited fashion before we release them to billions of people.
When you put it like that, the scale of it is scarily comprehensible.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#27Is this possible with NodeJS + express already? I didn't see any package for that or config
Node.js v15.0 now has experimental QUIC support. For production usage, I wouldn't expect anything usable before the v16 LTS release in October 2021 (and it might still be feature flagged at that point).
But that's pretty irrelevant for most production deployments, as you'll almost certainly want to have some type of AWS ALB, nginx, Cloudflare etc. load balancer in front of your Node services.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#28Is this possible with NodeJS + express already? I didn't see any package for that or config
QUIC support has landed behind an experimental flag https://github.com/nodejs/node/issues/23064
As for HTTP/3 that’s a bit further down the line
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#29> we refer to QUIC and HTTP/3 together as QUIC My understand is that HTTP/3 always means QUIC is used according to the standard. But that QUIC can be used for other protocols as well. FB's terminology seems to be backwards.
It's rather frustrating when people do this; for the rest of the article, when saying QUIC do they mean theur terminology that is actually QUIC and HTTP/3 or do they mean QUIC the TCP alternative? They use both.
As I said below, the blog is more focused on QUIC itself rather than HTTP/3. The bulk of the improvements we see are from QUIC as a transport layer, rather than the changes in HTTP/3.
Re: The majority of Facebook's traffic now uses QUIC and HTTP/3
#30For Chrome users, this open source extension will tell you what protocol the browser is using for each website being accessed: https://chrome.google.com/webstore/detail/http-indicator/hgc...
Unfortunately permissions to access everything on every website are way to broad for a niche extension like this. There's no guarantee it won't be sold to a malware developer in a month. If you want to use it, I suggest cloning the repo and loading it as an unpacked extension to avoid auto updates.
Also be sure to audit it yourself beforehand if you're going to go that route; there's no use tilting against auto-updates if you haven't gone to the trouble of making sure that malicious code isn't already present.