othernoel

Like SPDY (currently standartized as HTTP/2) there can be protocol version mismatches, that can result in errors. Please use default browser settings

The problem occurs with default browser settings. It seems the default for “Experimental QUIC Protocol” is “enabled.” This occurred in Chrome, Firefox, and Vivaldi, on Windows 11 and Linux Mint 22. It also occurred on Fedora 40, but I didn’t test multiple web browsers on it.

I have forwarded your topic url to Slack’s #meta channel, you can join and follow up there

Thanks. ??

https://quic.nginx.org/quic.html

You can also disgnose if your browser correctly handles QUIC and there are no obstacles like UDP filtering on the route from your ISP

The first time it showed 100 green (QUIC) blocks, and 900 red (failed) blocks, and the rest became HTTP. I re-ran the test and it was all HTTP. I assume that by default Chrome switches off QUIC if requests start failing from a website? In that case, it’s rather weird because that didn’t seem to happen when I was having trouble with www.remarpro.com.

Perhaps the problem is that www.remarpro.com loaded partially instead of failing completely? In some cases only half of the text of the webpage would load, meaning the connection would be closed while in progress for some reason.

To my knowledge, only www.remarpro.com and Tumblr fail to load like this. I never had trouble with any other website.

I just checked and this issue also seems to affect all websites hosted on wordpress.com.