r3dfox, a modern Firefox based web browser for Windows Vista, 7, and 8!

[The-10-Pen]

These UDP and TCP exist in "real" Firefox, ie, not a fork but the "real" Firefox.
You don't like me saying this, but IceCat does not have these.
It's all tied to background connections. DNS, TCP, UDP, all of the above.

2026-05-06_13-09-27.jpg (155.97 KiB) Viewed 64 times

[Duke]

IceCat does not have these.

Latest version of Icecat for Windows I've found is v115.24.0 which is based on Firefox ESR with the same version number.
I actually have Firefox v115.35.1 ESR installed and it behaves like Icecat but the base of these versions is quite old now. There have been many changes since Firefox 128 and 140 so I think v150 is closer to v140 than to v115.

And don't forget my troubles occur when using Quad9 with the Max Protection setting of the DNS over HTTPS so in case of failure there should be no fall back at all in any case but an error/warning message.

[The-10-Pen]

Agreed. Icecat is at 140.3.1, but only for Linux. The Windows distribution is basically "abandonware".

[The-10-Pen]

But my main point kind of remains, this is an "upstream" issue with all of the under-the-hood changes from Official Upstream Real v14x.y and Official Upstream Real v150.z.

[The-10-Pen]

There is also a problem with the HTTP Version field.

This is also an "upstream" issue.
"Real" Firefox has this bug, therefore **ALL** forks will have this bug.
If you want a challenge, try to find *any* 'fox fork that doesn't have this issue.
It's not the ekx-forget-his-name fork that was requested to check if it occurs there.
Since it is in "real" 'fox, it's going to be in *ALL* forks of 'fox.

Untitled.jpg (209.03 KiB) Viewed 31 times