3 ms·
"In fact, the blog post you’re reading right now was probably loaded over HTTP/3!" It actually isn't. But some of the 3rd party resources like a captcha script
by weird-eye-issue 3y ago
"In fact, the blog post you’re reading right now was probably loaded over HTTP/3!"
It actually isn't. But some of the 3rd party resources like a captcha script are loaded over HTTP3
- diggan 3y agoSeeing the same thing both in Firefox and Chrome, every response from blog.apnic.net comes over HTTP/2, none of the HTTP/3 ones are from any apnic.net requests. Strange that a registry, who should have really good idea about what kind of infrastructure they run, would get which protocol they're using wrong.
- krichprollsch 3y agoThe original blog post is served hover http/3 as far as I can see. https://pulse.internetsociety.org/blog/why-http-3-is-eating-the-world https://pulse.internetsociety.org/blog/why-http-3-is-eating-...
- dgb23 3y agoLooks like they forgot that we are hitting a cache that isn't configured the same way.
- weird-eye-issue 3y agoAppears to be Cloudflare's APO cache. I wonder why they haven't toggled HTTP/3 on in their Cloudflare dashboard (Just confirmed my sites with APO are being served with HTTP/3)
- ReactiveJelly 3y agoAnd I can't use HTTP/3 over Tor cause Tor only forwards TCP lol We'll get there