ipfs/ipfs-companion

Firefox's new aggressive time out logic

Open

#1,051 创建于 2022年2月11日

在 GitHub 查看
 (2 评论) (1 反应) (0 负责人)JavaScript (1,992 star) (364 fork)batch import
P3area/firefoxexp/novicegood first issuehelp wanted

描述

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:

2022-02-11_19-09

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?)

贡献者指南

技术栈
javascript
领域
frontendperformance
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
understanding of Firefox network behaviorbasic IPFS knowledge
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the changes in Firefox around version 96-97 that led to increased timeout aggressiveness. Reproduce locally by loading a large directory like dist.ipfs.io.ipns.localhost:8080/go ipfs/v0.11.0 on first load. Check if there are any existing Firefox preferences or about:config flags that could mitigate the issue. Look at go ipfs response generation time and see if there is a way to speed up the initial block retrieval to avoid timeout.