On 4/27/23 20:59, Tristan wrote:
Then yep, you're in the same boat as we were. It switched for no reason one day. Even trying HTTPS/SVCB DNS records did nothing for us until it "magically" decided to use H3.
Today it is using h3. I didn't change anything, other than installing updates on my desktop (including the kernel) and rebooting it. Which might cause infinitesimal differences in timing. Firefox hasn't been updated in a few days.
When I try to get a response locally using a curl docker container that supports http3, the request times out. If I use that curl to pull www.google.com, that works.
The same sites that timeout with that version of curl now work in Firefox and Chrome using http3 on the same client system, and test OK on http3check.net. I don't understand that at all. This is the docker command you can try yourself:
docker run --rm ymuski/curl-http3 curl -v -m 5 -s -f "https://www.google.com/"; --http3
Redirect stdout to /dev/null to more easily see the h3/tls negotiation. Thanks, Shawn
