3 ms·

Thanks to there always being fallback to older HTTP versions, I've never encountered an issue with HTTP/3 that prevented me from accessing a site. If HTTP/3 doe

• c4mpute 4y ago
  Hopefully, yes. But one can imagine a lot of weird problems with networks treating TCP and UDP differently such that HTTP/3 performance on UDP is degraded with no fallback to earlier TCP based versions happening, because your client will only fall back if there are errors.
• jillesvangurp 4y ago
  I think this article is specifically about running web servers inside of networks with firewalls that block udp on port 443 for whatever reason. There are lots of older networks that have such firewalls and they aren't going to get upgraded overnight. Reaching http3 servers outside those networks is indeed not a problem as the connection gets downgraded appropriately. You'd know this when Google, for example, stops working inside your network as most of their load balancers are serving http3. Users tend to complain about these things and this obviously hasn't been happening. Ergo, connections are being downgraded as you'd expect. But putting up webservers serving http3 in a network that blocks udp3 is indeed not going to work until somebody fixes the firewall. You could still do it and test if browsers from outside the network downgrade correctly. But that seems a bit pointless.
• xyst 4y ago
  Is it possible to catch, from the server side, when this happens? Or is this only a client side event? Would be interesting to see how many will requests get downgraded or not over a long period of time.