3 ms·
Rest easy, HTTP/3 and below have fallback mechanisms all the way back to HTTP 1.0, as long as you still keep TLS enabled. I'm not planning on blocking anything
by jeroenhd 4y ago
Rest easy, HTTP/3 and below have fallback mechanisms all the way back to HTTP 1.0, as long as you still keep TLS enabled. I'm not planning on blocking anything older than TLS 1.2 in my standard config.
I fully support user choice to disable whatever protocol they want. I also think modern browsers lack options in this department. If you dislike QUIC, which I can completely understand, you should disable it.
On the server side, though, you can use modern servers and tell all your clients to stick with HTTP 1.1. Let the people who do like QUIC (or don't care) get the benefit of faster page loads and lower latency. HTTP/2 and HTTP/3 solve some real performance issues, particularly for users with unstable or slow internet connections. I don't see why would would deprive them of that simply because you prefer to have the protocol disabled.
- ocdtrekkie 4y agoThat's a reasonable position. And don't get me wrong, I understand there are situations and reasons as a client to want these tools available. But networks often block them for security reasons, and it's their network and prerogative to do it as a condition to use the network.