Firefox's new aggressive time out logic

[lidel]

Seems that Firefox (around version 96-97) changed somethign and is now way more aggresive when a gateway does not start returning response immediately.

For example, first load (empty ipfs repo) of http://dist.ipfs.io.ipns.localhost:8080/go-ipfs/v0.11.0 in Firefox 97 produces:

Usually hitting F5 solves the issue, because by that time, the IPFS node already has blocks and can generate the response.

TODO

• [ ] needs analysis (what changed, what is the trigger, is there anything we could do in companion or go-ipfs to avoid this annoyance?)

[lidel]

If anyone from the community has time to dig into this and post comment with findings on this issue, that would be really appreciated :pray:

[RubenKelevra]

I can confirm this issue. This is related to Firefox https-only mode.

If you activate it, you have like a 3-second timeout window for time for first byte (as it seems).

If you deactivate it, the issue is gone.

While I think this is a Firefox bug, we might just want to make an exception until it's fixed upstream.

Edit: Making an exception doesn't work, as there are no wildcards allowed, only specific hostnames can be excluded.