[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTlah42EkXqXnfShHi-a1yqvbgqC84luNRUBUWaza0Bg":3},{"item":4,"related":44},{"id":5,"type":6,"title":7,"slug":8,"summary":9,"body":10,"coverUrl":11,"productScreenshots":12,"productLinks":13,"authorName":14,"authorUrl":15,"authorSubject":16,"category":17,"tags":22,"sourceLabel":35,"sourceName":36,"sourceUrl":37,"status":38,"seoTitle":7,"seoDescription":9,"canonicalUrl":35,"isFeatured":39,"sno":40,"sortOrder":41,"publishedAt":42,"updatedAt":43,"createdAt":43},"1d9484b9-7a31-4636-9070-502f78d05549","article","Happy Eyeballs：IPv6 连不上，浏览器为什么不用干等？","happy-eyeballs-dual-stack-connection-strategy","Happy Eyeballs 通过错开多个地址族的连接尝试，减少双栈网络中单一路径慢或不可达造成的等待。本文解释竞速策略与资源取舍。","一台手机同时有 Wi-Fi、蜂窝网络和多种地址协议，连接网站时可能先拿到 IPv6 地址，也可能只能经 IPv4 到达目标。若客户端先尝试一种地址并长时间等待失败，再尝试另一种，用户就会觉得网页“明明有网，却要卡一下”。Happy Eyeballs 是一组让连接尝试更灵敏的技术建议，目标是在多地址、多协议环境中尽快取得可用连接。\n\n它通常不会让客户端完全放弃 IPv6 或盲目并发所有尝试，而是先解析可用地址，再错开启动不同候选连接的时间。客户端可以优先尝试某一地址族，同时在短暂等待后启动另一种选择；哪个连接先成功，就使用哪个，并取消或清理不再需要的尝试。用户看到的是连接更快恢复，系统则在速度与避免无谓竞争之间折中。\n\n为什么不同时把所有候选地址一股脑发起？并行越激进，越可能浪费连接、端口和服务器资源，也可能让不同地址族的流量偏向不符合预期。RFC 建议对 DNS 查询、地址排序和连接尝试进行协调，避免因单一地址不可达而让整个页面加载被拖住，同时尽量保留对 IPv6 等路径的偏好。\n\nHappy Eyeballs 并不能修复网络本身，也不保证每次都选中“理论上最近”的服务器。它只是让客户端有机会绕开某个慢或不可达的候选路径；DNS 延迟、代理设置、防火墙、服务器健康和网络切换仍会影响体验。连接在一个地址族成功后，中途网络环境改变，应用可能还需要自己的重连和会话迁移逻辑。\n\n当你发现网站在某些 Wi-Fi 或 VPN 环境里首次打开特别慢，之后刷新却快很多，双栈连通性问题可能是排查方向之一，但缓存也会造成类似现象。浏览器、操作系统和应用的实现细节各异，应结合 DNS 与连接时间线分析，而不是仅凭“IPv6 开了”就认定原因。\n\n这个名字听起来像魔法，其实是工程上的竞速与回退策略：尊重多种可用路径，让客户端在不可靠网络里尽早找到第一条真正走得通的路。\n\n来源：[RFC 8305：Happy Eyeballs Version 2](https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc8305.html)","\u002Fuploads\u002F2026-10-06\u002F820c2d7a-e3d5-470d-b324-665310253cde.jpg",[],[],"Foundit","https:\u002F\u002Ffoundit.cn","foundit-ai-editorial",{"id":18,"name":19,"slug":20,"description":21},"6179d3b6-dc34-4483-9ded-3cd9f1b37a47","科普","abbreviation","介绍各领域新兴概念",[23,27,31],{"id":24,"name":25,"slug":26},"7c76bfc2-f80f-4ee0-a95d-27bd8708b434","技术","slug",{"id":28,"name":29,"slug":30},"a202d639-99a6-488a-a712-4d4c6ffd7e15","开发","dev",{"id":32,"name":33,"slug":34},"4c2bbea6-eab7-40a8-8447-1de478ff7749","分析","analyse",null,"RFC 8305：Happy Eyeballs Version 2","https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc8305.html","published",false,53,0,"2026-10-06T00:00:00.000Z","2026-10-06T07:51:37.596Z",[45,54,63],{"id":46,"type":6,"title":47,"slug":48,"summary":49,"coverUrl":50,"authorName":14,"sno":51,"publishedAt":52,"createdAt":53},"9ccde95c-d754-4808-91f7-488f392e3eeb","你的品牌在AI眼里到底存不存在？这套系统说了算","automated-geo-monitoring-system","靠手动抽查来验证GEO效果，本质上是在跟概率玩游戏。赢一次，不代表能一直赢。","\u002Fuploads\u002F2026-08-07\u002Fdf111c0d-f14a-4b2a-8347-141e96b71654.jpg",1,"2026-08-07T00:00:00.000Z","2026-08-07T04:31:30.843Z",{"id":55,"type":6,"title":56,"slug":57,"summary":58,"coverUrl":59,"authorName":14,"sno":60,"publishedAt":61,"createdAt":62},"9865c835-21fc-4f74-b154-19c054173557","fscrypt：只给手机里的某个文件夹加密，系统怎么做到？","linux-fscrypt-file-based-encryption","Linux fscrypt 在支持的文件系统中为目录树、文件内容和文件名提供文件级加密。它与整盘加密保护的范围不同，也不会隐藏所有文件系统元数据；本文从解锁密钥说到备份与恢复的边界。","\u002Fuploads\u002F2026-10-17\u002Fdec803fe-0da3-4a9e-8ffc-47427cf599d6.jpg",41,"2026-10-17T00:00:00.000Z","2026-10-17T03:08:37.641Z",{"id":64,"type":6,"title":65,"slug":66,"summary":67,"coverUrl":68,"authorName":14,"sno":69,"publishedAt":70,"createdAt":71},"56d3ebcb-170a-4f96-9134-ae85fb65542b","DANE\u002FTLSA：DNSSEC 能否帮助验证网站的 TLS 证书？","dane-tlsa-dnssec-tls-authentication","DANE 使用 DNS 中的 TLSA 记录发布与 TLS 服务证书或公钥相关的约束，并依赖 DNSSEC 验证记录来源。本文解释它如何补充信任路径，以及为什么它不等于所有网站都能抛弃 CA。","\u002Fuploads\u002F2026-10-13\u002F8c7d9bf5-62c6-47d4-b8eb-c4db7a21fa61.jpg",42,"2026-10-13T00:00:00.000Z","2026-10-13T02:13:55.563Z"]