News for hackers. Stuff that matters.
Re:The Status of HTTP/3 by profmonocle on Monday January 13, 2020 @05:56PM (#22039675)
> I am afraid that businesses that will host HTTP/3 will be less secure in terms of availavility.

Presumably most HTTP/3 implementations will gracefully fall back to HTTP/2 (or 1.1) if UDP is filtered. Chrome's existing QUIC implementation already does this.

Every Google property has had QUIC enabled for quite a while now (at least 4-5 years), so if UDP blocking would cause availability issues, affected businesses would've noticed by now.

Re:The Status of HTTP/3 by wahern on Monday January 13, 2020 @07:10PM (#22040283)
In 2017 Google reported that "4.4% of clients are unable to use QUIC". See sec. 7.2 of https://static.googleusercontent.com/media/research.google.c....
Re:The Status of HTTP/3 by profmonocle on Monday January 13, 2020 @10:39PM (#22041624)
Sure, but that doesn't mean those clients are unable to connect to QUIC-enabled domains. Chrome detects that the UDP packets are being lost, disables QUIC, and falls back to HTTP/2.