[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:mobile-dns-proxy-routing-check":3,"blog-article:\u002Fblog\u002Fmobile-dns-proxy-routing-check":986,"blog-related:\u002Fblog\u002Fmobile-dns-proxy-routing-check":987,"blog-translations:\u002Fblog\u002Fmobile-dns-proxy-routing-check":988},{"available":4,"article":5,"relatedArticles":155,"translations":895},true,{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":18,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":23,"bodyHtml":154},"strapi",4458,"uhv6asxd0saf1niyacil54j0","zh","mobile-dns-proxy-routing-check","\u002Fblog\u002Fmobile-dns-proxy-routing-check","移动端 DNS 请求是否经过代理怎么检查","检测页面不能单独证明 DNS 请求是否经过代理。结合设备观察、应用日志和出口对照，区分解析路径与代理出口，并限定结论范围。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_dns_cover_283dd444a4.webp","2026-11-18T02:35:45.137Z","2026-11-18T02:35:45.123Z","Global Proxies Team",[],false,0,2,"blocks",[24,30,35,39,43,62,66,77,81,85,89,106,110,120,125,129,133,138,142,146,150],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"检测页面显示运营商 DNS 时，不能据此断定 App 绕过了代理。先区分 DNS 查询由谁完成、后续连接从哪里出去，再结合设备或客户端证据判断。","text",{"type":31,"level":21,"children":32},"heading",[33],{"text":34,"type":29},"先区分 DNS 解析路径和代理出口",{"type":25,"children":36},[37],{"text":38,"type":29},"本地解析和代理出口可以同时存在：查询可能由本地网络完成，而连接仍经代理发出；反过来也可能。确认时应分别记录解析器与连接出口。",{"type":31,"level":21,"children":40},[41],{"text":42,"type":29},"检测页面能否确认 DNS 请求经过代理？",{"type":25,"children":44},[45,47,53,55,60],{"text":46,"type":29},"很多检测页面会显示 DNS 服务器或 DNS 地区，但结果通常只反映本次页面请求。浏览器或系统的安全 DNS 设置、解析缓存和上游递归解析都可能影响显示结果；DoH（",{"text":48,"type":29,"marks":49},"RFC 8484",[50],{"href":51,"type":52},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc8484","link",{"text":54,"type":29},"）与 DoT（",{"text":56,"type":29,"marks":57},"RFC 7858",[58],{"href":59,"type":52},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc7858",{"text":61,"type":29},"）还会加密查询内容。HTTP 代理通常由代理侧解析目标域名，SOCKS5 则可由客户端解析，实际路径仍取决于客户端实现。因此，检测页适合提供线索，不能据此推断设备上其他 App 或后台请求的解析方式。",{"type":31,"level":21,"children":63},[64],{"text":65,"type":29},"如何在设备上观察 DNS 请求？",{"type":25,"children":67},[68,70,75],{"text":69,"type":29},"设备侧观察可以记录本机发出的查询、时间和目标解析器，方式包括系统网络诊断、开发者工具或授权环境下的抓包。它能补充本机请求路径的证据，但不一定能显示最终由哪个上游完成解析；使用加密 DNS 时，查询内容也可能不可见。没有抓到明文查询，不代表没有发生 DNS 请求。操作前应确认设备可控并已获授权，抓取内容按敏感数据处理。需要进一步验证时，可参考",{"text":71,"type":29,"marks":72},"代理 DNS 解析路径测试",[73],{"href":74,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-dns-resolution-path-testing",{"text":76,"type":29},"。",{"type":31,"level":21,"children":78},[79],{"text":80,"type":29},"如何利用应用和客户端日志检查 DNS 请求？",{"type":25,"children":82},[83],{"text":84,"type":29},"应用或客户端日志可以把已记录的域名和连接对应到具体功能，例如一次同步或某个接口请求。不过，日志覆盖面取决于实现：有的只记录失败请求，有的只记录主接口。没有日志记录不能证明请求没有发生，因此应先确认日志覆盖哪些功能和请求阶段，再据此判断。",{"type":25,"children":86},[87],{"text":88,"type":29},"要核对某次 App 请求，可按以下步骤收集证据：",{"type":90,"format":91,"children":92},"list","ordered",[93,98,102],{"type":94,"children":95},"list-item",[96],{"text":97,"type":29},"在自有域名下使用本次唯一的查询名，记录目标 App、版本、时间和请求编号（`caseID`）。",{"type":94,"children":99},[100],{"text":101,"type":29},"确认该实现由本地还是代理侧解析，再用 `caseID` 和时间对照客户端解析日志、解析器或权威 DNS 记录，以及后续目标请求。注意区分代理入口主机名和业务目标域名的解析。",{"type":94,"children":103},[104],{"text":105,"type":29},"如果查询可能命中缓存，或 DoH／DoT 内容不可见，就把解析路径标为“无法确认”；没有明文查询不等于没有 DNS 请求。手机侧缺少观察手段时，需要开发者或客户端日志补证，不能用浏览器样本代替目标 App。",{"type":31,"level":21,"children":107},[108],{"text":109,"type":29},"三种检查方法分别能证明到哪一步？",{"type":25,"children":111},[112,114,119],{"text":113,"type":29},"三种证据适合回答的问题不同，可按需要组合使用。若 DNS 仍显示本地运营商，可继续看",{"text":115,"type":29,"marks":116},"代理后 DNS 显示本地运营商的排查方法",[117],{"href":118,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-dns-local-isp-leak-troubleshooting",{"text":76,"type":29},{"type":121,"children":122},"code",[123],{"text":124,"type":29},"| 方法 | 能观察到什么 | 不能单独据此判断什么 |\n| --- | --- | --- |\n| 检测页面 | 本次页面请求显示的解析结果与出口线索 | 设备上其他 App 或后台请求的解析路径 |\n| 设备侧观察 | 本机发出的查询、时间和目标解析器 | 最终由哪个上游完成解析；加密查询的具体内容 |\n| 应用或客户端日志 | 日志实际记录的请求及对应功能 | 未记录的请求是否发生；日志是否覆盖全部流量 |",{"type":25,"children":126},[127],{"text":128,"type":29},"三种方法可以一起使用，但不能互相替代。若结果只覆盖某个 Wi-Fi 网络和某个 App 版本，应在记录中注明；更换网络或版本后需要重新检查。",{"type":31,"level":21,"children":130},[131],{"text":132,"type":29},"常见问题",{"type":31,"level":134,"children":135},3,[136],{"text":137,"type":29},"检测页面显示本地运营商 DNS，就一定没走代理吗？",{"type":25,"children":139},[140],{"text":141,"type":29},"不一定。页面反映的是那一次请求的解析结果与出口，可能来自本地网络，也可能因为代理链路把解析交给了本地侧。要判断设备上的解析路径，还需要设备侧或应用侧的记录作为补充。",{"type":31,"level":134,"children":143},[144],{"text":145,"type":29},"手机上抓 DNS 请求需要什么条件？",{"type":25,"children":147},[148],{"text":149,"type":29},"需要可控的设备、明确的授权，以及在目标设备上可用的观察手段，例如系统网络诊断、开发者工具或授权环境下的抓包。抓到的内容按敏感数据管理，只保留结论所需的字段。",{"type":25,"children":151},[152],{"text":153,"type":29},"更新时间：2026-11-16","",[156,399,620],{"source":6,"id":157,"documentId":158,"translationKey":158,"locale":9,"slug":159,"path":160,"_path":160,"title":161,"description":162,"excerpt":162,"image":163,"publishedAt":164,"updatedAt":165,"author":17,"tags":166,"featured":19,"sortOrder":20,"readingTime":134,"bodyType":22,"bodyBlocks":167,"bodyHtml":154},4550,"gqryzu9nle8pzuzfzsq99ca4","mobile-proxy-troubleshooting-log-fields","\u002Fblog\u002Fmobile-proxy-troubleshooting-log-fields","移动端代理问题需要收集哪些日志信息","代理 IP 排障日志的价值在于别人能否按同一条件复现。按必须、可选、禁止三档收字段，导出前删掉凭据与个人标识，再按时间和设备命名打包，缺一项就补一项。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_47c42e5b14.webp","2026-11-19T03:28:14.371Z","2026-11-19T03:28:14.354Z",[],[168,172,176,180,191,195,199,203,207,211,215,219,223,227,279,289,293,304,308,312,316,320,342,346,349,353,357,361,365,369,373,377,381,385,389],{"type":25,"children":169},[170],{"text":171,"type":29},"排障日志的价值不在多，而在\"别人能不能按同一条件复现\"。手机端尤其容易丢信息：系统日志滚动快、应用日志分散，连接记录也可能包含账号标识或认证信息，导出前应先检查并脱敏。",{"type":25,"children":173},[174],{"text":175,"type":29},"先按\"必须、可选、禁止\"列出字段，收集后检查敏感信息，再按时间和设备命名打包。这样既方便排查，也能减少凭据或个人信息外泄。",{"type":31,"level":21,"children":177},[178],{"text":179,"type":29},"移动端代理故障日志需要记录哪些关键信息",{"type":25,"children":181},[182,184,189],{"text":183,"type":29},"最小记录集合应包含：时间（含时区）、网络类型、目标地址与协议、错误类型或状态码、出口地区、客户端版本、设备与系统版本、失败阶段、观察来源、复现步骤，以及事件／请求关联 ID；没有服务端 ID 时可用受控的 caseID。出口保留地区和同一审查范围内稳定化名，不要求公开真实 IP。若错误表现为连接重置，可参照",{"text":185,"type":29,"marks":186},"代理连接被重置要记录哪些证据",[187],{"href":188,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-connection-reset-evidence-record",{"text":190,"type":29},"补齐时间、错误码和链路记录。",{"type":25,"children":192},[193],{"text":194,"type":29},"时间和时区用于对齐事件，网络类型用于区分蜂窝与 Wi-Fi，目标地址和错误信息有助判断影响范围，复现步骤则决定接手人员能否重现现场。缺少关键字段会增加排查难度；暂时无法提供时，应标明缺失项，而不是用猜测补齐。",{"type":25,"children":196},[197],{"text":198,"type":29},"这些字段里最容易被忽略的是“出口地区”。同样一条失败记录，出口在国内和出口在新加坡，指向的原因完全不同。记录时写地区即可，不需要写完整 IP。",{"type":31,"level":21,"children":200},[201],{"text":202,"type":29},"哪些日志字段有助排查，哪些信息必须删除或脱敏",{"type":121,"children":204},[205],{"text":206,"type":29},"| 档位 | 字段 | 来源 | 说明 |\n| --- | --- | --- | --- |\n| 必须 | 时间与时区、网络类型、目标域名与协议、错误码或错误类型、出口地区或稳定化名、客户端与 App 构建版本、设备与系统版本、失败阶段、观察来源、事件／请求关联 ID（无服务端 ID 时用受控 caseID）、复现步骤 | 系统设置、客户端、目标站回显 | 网络类型只列一次；记录是否发生切换，发生时填写时间，未发生或未知也明确标出 |\n| 可选 | 信号强度、应用前后台状态、同一时段另一台设备的对照结果 | 系统状态、现场观察 | 按问题类型取舍；网络切换事件统一记在必填项中 |\n| 禁止 | Cookie、Authorization、完整查询串、手机号与邮箱、设备唯一标识、精确位置 | 应用日志、请求记录 | 导出前必须删除或替换 |",{"type":25,"children":208},[209],{"text":210,"type":29},"必填项应按表格逐项记录，其中“复现步骤”常被漏掉，却是他人还原问题的重要依据。",{"type":25,"children":212},[213],{"text":214,"type":29},"分档的意义是防止两种极端：一种是只发一句\"连不上\"，另一种是把整个日志包原样发出去。前者无法排查，后者泄露风险。",{"type":25,"children":216},[217],{"text":218,"type":29},"可选字段按问题类型补充：怀疑网络切换时，记录切换时间；怀疑后台限制时，补充应用前后台状态。",{"type":31,"level":21,"children":220},[221],{"text":222,"type":29},"导出日志前，先删除或遮盖这六类敏感信息",{"type":25,"children":224},[225],{"text":226,"type":29},"导出前重点检查六类信息：",{"type":90,"format":228,"children":229},"unordered",[230,239,247,255,263,271],{"type":94,"children":231},[232,237],{"text":233,"type":29,"marks":234},"认证凭据",[235],{"type":236},"bold",{"text":238,"type":29},"：Cookie、Authorization 头、API Key 和客户端令牌，泄露后可能被用于访问账号。",{"type":94,"children":240},[241,245],{"text":242,"type":29,"marks":243},"完整查询串",[244],{"type":236},{"text":246,"type":29},"：保留必要路径，去掉参数中的会话 ID、用户 ID 和签名，凭据和身份值应删除或用稳定占位符替代；经核对不敏感且有助复现的排序、分页和地区参数值可以保留。不能共享真实值时，提供等价虚构示例并标明替代关系。",{"type":94,"children":248},[249,253],{"text":250,"type":29,"marks":251},"个人标识",[252],{"type":236},{"text":254,"type":29},"：手机号、邮箱、姓名和身份证件号。",{"type":94,"children":256},[257,261],{"text":258,"type":29,"marks":259},"设备唯一标识",[260],{"type":236},{"text":262,"type":29},"：广告标识、硬件序列号和安装 ID。",{"type":94,"children":264},[265,269],{"text":266,"type":29,"marks":267},"精确位置",[268],{"type":236},{"text":270,"type":29},"：经纬度和详细地址；通常只需保留城市或地区。",{"type":94,"children":272},[273,277],{"text":274,"type":29,"marks":275},"业务敏感数据",[276],{"type":236},{"text":278,"type":29},"：订单内容、聊天记录和上传文件内容；排障通常只需要记录请求类型，不需要保留具体内容。",{"type":25,"children":280},[281,283,288],{"text":282,"type":29},"替换方式要统一：用 `[REDACTED]` 或 `***` 替换凭据与身份值，不保留原值长度等可能暴露特征的信息；同时保留经核对不敏感、复现所必需的排序、分页和地区参数。无法共享真实参数时，提供等价虚构示例并说明替代关系。也不要整段删除，否则看不出请求结构。日志该记录什么、不该记录什么，可对照 ",{"text":284,"type":29,"marks":285},"OWASP 日志记录速查表",[286],{"href":287,"type":52},"https:\u002F\u002Fcheatsheetseries.owasp.org\u002Fcheatsheets\u002FLogging_Cheat_Sheet.html",{"text":76,"type":29},{"type":31,"level":21,"children":290},[291],{"text":292,"type":29},"如何命名和打包日志，方便按时间定位问题",{"type":25,"children":294},[295,297,302],{"text":296,"type":29},"一个包只放一次复现：时间范围、设备、版本写在文件名里，例如\"时间范围-设备型号-系统版本-问题类型\"。包内附一份清单，说明每个文件对应哪一段操作。整理完成后，可按",{"text":298,"type":29,"marks":299},"代理网络故障如何制作最小复现记录",[300],{"href":301,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-fault-minimal-reproduction-record",{"text":303,"type":29},"检查现场是否可复现。",{"type":25,"children":305},[306],{"text":307,"type":29},"不要把几天的日志混在一个包里。时间跨度越大，定位越慢，也越容易把无关的账号信息带进去。",{"type":25,"children":309},[310],{"text":311,"type":29},"文件格式优先用原始文本或结构化导出，不要只发截图。截图可以作为补充，但不能替代原始记录——时间精度和字段完整性都会丢。",{"type":25,"children":313},[314],{"text":315,"type":29},"如果必须发截图，先检查状态栏、通知、账号头像、地址栏这些位置，它们经常带着身份信息。",{"type":31,"level":21,"children":317},[318],{"text":319,"type":29},"提交日志前，用五个问题检查材料是否完整",{"type":90,"format":91,"children":321},[322,326,330,334,338],{"type":94,"children":323},[324],{"text":325,"type":29},"别人拿着这份日志，能不能按写下的步骤复现一次？",{"type":94,"children":327},[328],{"text":329,"type":29},"时间是否带时区，是否与目标站记录能对上？",{"type":94,"children":331},[332],{"text":333,"type":29},"有没有哪一处还能看出账号、令牌或个人信息？",{"type":94,"children":335},[336],{"text":337,"type":29},"目标地址是否保留了域名和协议，去掉了敏感参数？",{"type":94,"children":339},[340],{"text":341,"type":29},"失败前后是否各留了一段观察窗口，而不是只有一条错误？",{"type":25,"children":343},[344],{"text":345,"type":29},"五个问题里有一个答不上来，就先补齐再提交。补齐的成本，通常比来回追问低。",{"type":31,"level":21,"children":347},[348],{"text":132,"type":29},{"type":31,"level":134,"children":350},[351],{"text":352,"type":29},"代理 IP 的日志可以整包发给支持方吗？",{"type":25,"children":354},[355],{"text":356,"type":29},"不建议。按时间窗截取，附本机时间与时区；整包既慢又扩大泄露面。",{"type":31,"level":134,"children":358},[359],{"text":360,"type":29},"截图里哪些信息必须打码？",{"type":25,"children":362},[363],{"text":364,"type":29},"头像、昵称、手机号、通知内容、地址栏参数、设备名称都要打码。只提供定位问题所需的最少信息。",{"type":31,"level":134,"children":366},[367],{"text":368,"type":29},"代理 IP 的主机和端口要不要一起提供？",{"type":25,"children":370},[371],{"text":372,"type":29},"默认先脱敏。确有排查需要时，只通过受控支持渠道按需提供，并限定访问范围与保留期限；账号、密码、令牌、签名及其他可用于认证的凭据必须遮盖。",{"type":31,"level":134,"children":374},[375],{"text":376,"type":29},"时间用本地时区还是 UTC？",{"type":25,"children":378},[379],{"text":380,"type":29},"都行，写明是哪一个并全篇统一。与目标站记录对照时换算到同一时区。",{"type":31,"level":134,"children":382},[383],{"text":384,"type":29},"工单里要不要附完整日志包？",{"type":25,"children":386},[387],{"text":388,"type":29},"先附最小复现包和清单，对方要哪段再补。一次给全反而难定位。",{"type":25,"children":390},[391,393,398],{"text":392,"type":29},"账号与接入问题可查看",{"text":394,"type":29,"marks":395},"帮助中心",[396],{"href":397,"type":52},"https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002FFaq\u002F",{"text":76,"type":29},{"source":6,"id":400,"documentId":401,"translationKey":401,"locale":9,"slug":402,"path":403,"_path":403,"title":404,"description":405,"excerpt":405,"image":406,"publishedAt":407,"updatedAt":408,"author":17,"tags":409,"featured":19,"sortOrder":20,"readingTime":134,"bodyType":22,"bodyBlocks":410,"bodyHtml":154},4549,"sbks9w6bc9gtratt9p27x35c","mobile-signal-fluctuation-vs-proxy-disconnect","\u002Fblog\u002Fmobile-signal-fluctuation-vs-proxy-disconnect","移动网络波动时如何区分代理断线与信号问题","移动网络波动与代理 IP 连接异常都可能导致请求失败。通过时间线对照网络切换、代理握手和目标站响应，判断下一步应检查接入网络、代理连接还是目标服务。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_4c3f4f8011.webp","2026-11-19T03:28:10.618Z","2026-11-19T03:28:10.598Z",[],[411,415,419,423,427,431,435,439,443,447,451,455,459,463,467,513,517,521,525,539,547,555,559,563,567,571,575,578,582,586,590,594,598,602,606,610],{"type":25,"children":412},[413],{"text":414,"type":29},"在地铁、电梯或人流密集处，手机请求失败很常见。这时代理 IP 断了和手机网络本身不稳，给出的现象几乎一样：转圈、超时、应用提示网络错误，只看一次失败分不出是哪一层。",{"type":25,"children":416},[417],{"text":418,"type":29},"先把网络切换、信号变化、代理连接和请求结果记在同一条时间线上。若换网络后问题消失，说明接入网络或对应配置可能相关；若问题持续存在，还要检查代理连接、认证、DNS 和目标站响应，不能只据此归因于代理侧。",{"type":31,"level":21,"children":420},[421],{"text":422,"type":29},"如何区分请求未发出和代理请求未收到响应",{"type":25,"children":424},[425],{"text":426,"type":29},"请求失败大致有两种情况：一种是尚未获得目标站的有效响应，例如域名解析失败、到代理入口的 TCP 连接未建立或 TLS 握手失败；这些现象可能发生在不同链路环节，需结合解析结果、连接目标和代理日志定位。另一种是连接已经建立，但等待响应时超时或中途被重置；此时目标站可能已经收到并处理请求，客户端却只看到超时，因此不能把“未收到响应”直接当作“目标端未执行”。",{"type":25,"children":428},[429],{"text":430,"type":29},"遇到 401、403、429 或验证码页面，先确认响应来源和失败阶段；按认证、限流或目标站规则处理，不把状态码本身当成信号或代理故障证据。",{"type":25,"children":432},[433],{"text":434,"type":29},"区分前两类，看三个地方：客户端有没有\"已连接\u002F已发送\"的记录；有没有收到状态码；错误是立刻出现还是等了一段时间才出现。三个都指向\"没发出去\"，就先按链路查；有\"已发送\"却无响应，才需要区分网络波动与代理断线。",{"type":31,"level":21,"children":436},[437],{"text":438,"type":29},"按时间线对照移动网络变化与代理连接状态",{"type":25,"children":440},[441],{"text":442,"type":29},"时间线只需要三个来源：系统网络状态（蜂窝或 Wi-Fi、切换时刻、飞行模式开关）、代理客户端的连接与认证事件（已连接、重连、认证失败）、请求本身（开始时间、错误类型、恢复时间）。三者用同一台设备的时钟记录，精确到秒，不要混用服务器时间。",{"type":25,"children":444},[445],{"text":446,"type":29},"记录的要求不是\"记得多\"，而是\"失败时刻前后各留一段观察窗口\"，长度按自己的任务节奏定。窗口里有切换事件、有重连事件、有请求结果，才谈得上判读。",{"type":25,"children":448},[449],{"text":450,"type":29},"下表为示例时间线，时间、状态码、信号格数和事件均为虚构，仅用于说明记录方式，不代表实测结果。",{"type":121,"children":452},[453],{"text":454,"type":29},"| 时间 | 网络类型与信号 | 是否发生切换 | 代理连接事件 | 请求结果 | 备注 |\n| --- | --- | --- | --- | --- | --- |\n| 09:12:03 | 蜂窝，2 格 | 否 | 已连接，出口 A | 200 | 基线条件 |\n| 09:14:20 | 蜂窝，1 格 | 否 | 已连接 | 请求超时 | 同时段另一台设备也超时 |\n| 09:15:02 | Wi-Fi | 是，蜂窝→Wi-Fi | 重连一次后已连接 | 200 | 切换后恢复 |\n| 09:18:40 | 蜂窝，3 格 | 是，Wi-Fi→蜂窝 | 重连中 | 连接被重置 | 在切换瞬间发起请求 |",{"type":25,"children":456},[457],{"text":458,"type":29},"表中六列是现场速记，够用来判断\"失败跟谁同时发生\"；要下结论还得补齐另外四项：目标 URL 与协议、状态码、出口地区、恢复动作。缺这四项，复测时无法确认第二次失败和第一次是不是同一件事。",{"type":25,"children":460},[461],{"text":462,"type":29},"一次只改一个变量：要判断切换的影响，就别同时换地点、换客户端版本、换目标域名。否则时间线再细，也只能说明\"当时确实失败了\"。",{"type":31,"level":21,"children":464},[465],{"text":466,"type":29},"对照网络切换、代理握手、信号强度和目标站响应",{"type":90,"format":228,"children":468},[469,477,485,499],{"type":94,"children":470},[471,475],{"text":472,"type":29,"marks":473},"切换",[474],{"type":236},{"text":476,"type":29},"：失败是否集中在网络切换后的短时间内。切换会重建路由和连接，这个窗口内的失败不能直接算到代理头上。",{"type":94,"children":478},[479,483],{"text":480,"type":29,"marks":481},"代理握手",[482],{"type":236},{"text":484,"type":29},"：客户端是否显示已连接、认证是否成功、有没有反复重连。认证失败、频繁重连更偏代理侧；一直显示已连接但请求不通，则要往下看目标响应。",{"type":94,"children":486},[487,491,493,498],{"text":488,"type":29,"marks":489},"信号强度",[490],{"type":236},{"text":492,"type":29},"：系统给的格数只是粗粒度值，格数下降说明无线环境变差，不等于数据连接一定不可用。它能提示\"该看网络侧了\"，不能单独作为结论。Android 上信号等级的含义见 ",{"text":494,"type":29,"marks":495},"SignalStrength 文档",[496],{"href":497,"type":52},"https:\u002F\u002Fdeveloper.android.google.cn\u002Freference\u002Fandroid\u002Ftelephony\u002FSignalStrength",{"text":76,"type":29},{"type":94,"children":500},[501,505,507,512],{"text":502,"type":29,"marks":503},"目标响应",[504],{"type":236},{"text":506,"type":29},"：有没有状态码、是不是只有某一个域名失败、换一个目标域名是否正常。只有一个域名失败，问题更可能在目标站或解析，而不是整条链路。连续断连的定位思路可参考",{"text":508,"type":29,"marks":509},"代理 IP 间歇性断开如何定位",[510],{"href":511,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-ip-intermittent-disconnect-diagnosis",{"text":76,"type":29},{"type":25,"children":514},[515],{"text":516,"type":29},"顺序上先看切换，再看代理握手：这两项在本地就有记录，几秒内能确认。信号强度放在第三位，它只提示该看网络侧；目标响应放最后，因为要换域名复测，成本最高。",{"type":25,"children":518},[519],{"text":520,"type":29},"这四项记录用于缩小故障范围：切换和握手可说明连接状态，信号强度只能作为网络侧线索，目标响应则帮助确认失败阶段。结合同一请求 ID、网络事件和错误信息再进一步判断；认证失败或频繁重连都不能单独证明故障来自代理。证据不足时写“倾向”或“暂无法区分”。",{"type":31,"level":21,"children":522},[523],{"text":524,"type":29},"根据测试结果判断应排查移动网络还是代理连接",{"type":25,"children":526},[527,531,533,538],{"text":528,"type":29,"marks":529},"更像接入网络问题",[530],{"type":236},{"text":532,"type":29},"：失败反复出现在网络切换或弱信号时段，且相同代理在其他网络下可正常连接。可固定目标和配置复测，并检查 DNS、网络切换时机与客户端超时设置；这些现象是判断线索，不能单独证明故障来源。如果客户端显示在线但请求仍超时，可对照",{"text":534,"type":29,"marks":535},"客户端显示在线但请求超时",[536],{"href":537,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-client-online-but-request-timeout",{"text":76,"type":29},{"type":25,"children":540},[541,545],{"text":542,"type":29,"marks":543},"更像代理连接问题",[544],{"type":236},{"text":546,"type":29},"：不同接入网络下都无法完成代理握手，且代理后台没有成功连接记录。此时可核对地址、端口、认证信息和服务状态；若代理连接已建立，则继续依据目标站响应排查。",{"type":25,"children":548},[549,553],{"text":550,"type":29,"marks":551},"无法区分",[552],{"type":236},{"text":554,"type":29},"：两层同时异常，或者观察窗口里既没有切换也没有重连记录。这时缩小变量——固定一个网络、只发一个请求、只打一个域名——再复测一次，不要在这个状态下下结论。",{"type":25,"children":556},[557],{"text":558,"type":29},"常见分支：只有某个 App 失败，先怀疑应用侧的代理支持差异；只有某个域名失败，先查目标站与解析；所有请求都失败且客户端显示离线，先查客户端与账号。这三种情况都不适合用\"换一批 IP 试试\"开始诊断，换 IP 会把现场清掉，下一次复现又要从头来。",{"type":31,"level":21,"children":560},[561],{"text":562,"type":29},"记录复测条件，避免用一次失败下结论",{"type":25,"children":564},[565],{"text":566,"type":29},"最小记录集合包括：测试时间、网络类型与信号、是否切换、代理连接事件、目标 URL、协议、状态码、出口地区、恢复动作、复测结果。缺了\"时间、网络、目标、结果\"四项，记录就无法复现。",{"type":25,"children":568},[569],{"text":570,"type":29},"复测尽量保持地点、网络类型、目标和时段一致，并记录观察窗口与样本范围。有限样本只能说明这几次的表现。结果不一致可能来自环境变化、间歇故障或目标变化，应保留各次记录并标为“待复测”。",{"type":25,"children":572},[573],{"text":574,"type":29},"停止条件也要提前定：按事先定好的次数跑完、结果一致就停；出现账号异常、验证码或需要重新认证时立即停止，不要为了追求样本量反复切网。整个过程只用自有或获授权设备，日志导出前先脱敏。",{"type":31,"level":21,"children":576},[577],{"text":132,"type":29},{"type":31,"level":134,"children":579},[580],{"text":581,"type":29},"开关一次飞行模式，能当代理 IP 断线的复现手段吗？",{"type":25,"children":583},[584],{"text":585,"type":29},"能当一次\"网络重建\"。但它同时改注册网络、连接与代理会话，只能证明重建后是否恢复。",{"type":31,"level":134,"children":587},[588],{"text":589,"type":29},"同一代理 Wi-Fi 正常、蜂窝失败，先查哪边？",{"type":25,"children":591},[592],{"text":593,"type":29},"先对照蜂窝与 Wi-Fi 下的网络类型、代理配置和连接记录，再检查运营商覆盖及客户端是否为不同网络分别保存了代理设置。",{"type":31,"level":134,"children":595},[596],{"text":597,"type":29},"手机读不到信号强度，时间线还成立吗？",{"type":25,"children":599},[600],{"text":601,"type":29},"成立。用网络类型变化、切换时刻、能否解析与建连替代，格数只作参考。",{"type":31,"level":134,"children":603},[604],{"text":605,"type":29},"同事的设备能连、我的不能，算代理问题吗？",{"type":25,"children":607},[608],{"text":609,"type":29},"先确认两台是否同一出口、同一目标、同一时段。三项有一项不同，就不能对比。",{"type":25,"children":611},[612,614,619],{"text":613,"type":29},"需要查具体接入入口时，可查看",{"text":615,"type":29,"marks":616},"代理设置帮助",[617],{"href":618,"type":52},"https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings",{"text":76,"type":29},{"source":6,"id":621,"documentId":622,"translationKey":622,"locale":9,"slug":623,"path":624,"_path":624,"title":625,"description":626,"excerpt":626,"image":627,"publishedAt":628,"updatedAt":629,"author":17,"tags":630,"featured":19,"sortOrder":20,"readingTime":134,"bodyType":22,"bodyBlocks":631,"bodyHtml":154},4548,"m5w5f52o4gq0p4hqfasgz4h8","long-proxy-task-interruption-avoid-duplicate-processing","\u002Fblog\u002Flong-proxy-task-interruption-avoid-duplicate-processing","长时间代理请求中断如何避免重复处理数据","通过代理运行的长任务中断后，未收到响应不代表目标端未处理。本文说明如何用业务主键或幂等键记录状态，并在恢复前核对目标端，避免重复写入或提交。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_cover_d3b959f788.webp","2026-11-19T03:28:04.700Z","2026-11-19T03:28:04.674Z",[],[632,636,640,644,648,652,656,682,700,704,708,742,746,750,754,765,769,773,807,817,821,825,829,833,837,841,845,849,853,856,860,864,868,872,876,880,884,888],{"type":25,"children":633},[634],{"text":635,"type":29},"长任务通过代理 IP 运行时连接中断，重新执行可能造成重复写入、提交或计费。常见原因是恢复逻辑把\"未收到响应\"误当成\"目标端未执行\"。",{"type":25,"children":637},[638],{"text":639,"type":29},"要避免这一点，先别急着找断点，先回答\"这一条到底处理完没有\"。把每条数据的处理状态做成可查询的，恢复时按状态决定跳过、重试还是转人工。网络恢复只是继续跑的前提，不是数据完整的证明。",{"type":31,"level":21,"children":641},[642],{"text":643,"type":29},"请求中断后，哪些情况可能导致数据被重复处理",{"type":25,"children":645},[646],{"text":647,"type":29},"重复处理通常来自几种情况：请求已到达目标端但回执丢失，客户端将超时当成失败后再次发送；写入成功后、更新本地完成状态前进程崩溃，恢复时又把数据当成未处理；多个工作进程同时领取同一批数据；或者客户端与中间层分别触发重试。检查点只能说明任务跑到哪里，不能证明这一条是否已经落地。因此，应结合客户端发送记录、目标端查询和业务侧可对账标识判断；证据不足时，将状态标为“结果未知”，不要仅凭客户端日志认定成功或失败。",{"type":31,"level":21,"children":649},[650],{"text":651,"type":29},"如何选择业务 ID、幂等键或内容指纹作为去重键",{"type":25,"children":653},[654],{"text":655,"type":29},"去重键的作用，是让同一条逻辑数据在任何一次重放中都能被认出来。三种常见做法各有前提：",{"type":90,"format":228,"children":657},[658,666,674],{"type":94,"children":659},[660,664],{"text":661,"type":29,"marks":662},"业务主键",[663],{"type":236},{"text":665,"type":29},"：订单号、任务 ID、URL 加版本号。最可靠，前提是目标端也用同一个键。",{"type":94,"children":667},[668,672],{"text":669,"type":29,"marks":670},"客户端幂等键",[671],{"type":236},{"text":673,"type":29},"：每条逻辑数据生成一次，重试时复用同一个键，不按\"第几次尝试\"生成。按尝试生成等于没有幂等。",{"type":94,"children":675},[676,680],{"text":677,"type":29,"marks":678},"内容指纹",[679],{"type":236},{"text":681,"type":29},"：对请求体做哈希。适合没有业务主键的场景，但内容一变指纹就变，还存在碰撞可能，只能作辅助。",{"type":25,"children":683},[684,686,691,693,698],{"text":685,"type":29},"幂等键只有在目标端认识并按约定去重时才有效；客户端自己记录键，不会让目标端自动去重。HTTP 方法本身的幂等语义见 ",{"text":687,"type":29,"marks":688},"RFC 9110 第 9.2.2 节",[689],{"href":690,"type":52},"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc9110#section-9.2.2",{"text":692,"type":29},"；迟到请求与安全重试的设计可参考 ",{"text":694,"type":29,"marks":695},"AWS Builders’ Library：Making retries safe with idempotent APIs",[696],{"href":697,"type":52},"https:\u002F\u002Faws.amazon.com\u002Fbuilders-library\u002Fmaking-retries-safe-with-idempotent-APIs\u002F",{"text":699,"type":29},"。键的粒度也要与可能重复的操作层级一致：粒度太粗会把不同操作合并，太细又无法识别重放。",{"type":31,"level":21,"children":701},[702],{"text":703,"type":29},"用四种处理状态判断任务中断后能否安全重试",{"type":25,"children":705},[706],{"text":707,"type":29},"四个状态足够覆盖大多数长任务。",{"type":90,"format":228,"children":709},[710,718,726,734],{"type":94,"children":711},[712,716],{"text":713,"type":29,"marks":714},"待处理",[715],{"type":236},{"text":717,"type":29},"：尚未发出。",{"type":94,"children":719},[720,724],{"text":721,"type":29,"marks":722},"处理中",[723],{"type":236},{"text":725,"type":29},"：已发出，未收到确定结果。进程崩溃后，这个状态不能自动回到待处理。",{"type":94,"children":727},[728,732],{"text":729,"type":29,"marks":730},"已完成",[731],{"type":236},{"text":733,"type":29},"：收到明确成功，或目标端确认存在。",{"type":94,"children":735},[736,740],{"text":737,"type":29,"marks":738},"结果未知",[739],{"type":236},{"text":741,"type":29},"：处理中超时、连接中断、进程崩溃后无法确认。",{"type":25,"children":743},[744],{"text":745,"type":29},"关键规则只有一条：处理中和结果未知，都必须先核对目标端，再决定去向，不得直接重置为待处理。恢复时允许的动作也只有三种——跳过（已确认完成）、重试（确认未完成）、转人工（无法确认且重放有副作用风险）。",{"type":25,"children":747},[748],{"text":749,"type":29},"状态要写到能跨进程重启的位置，并且每次变化都写，而不是任务结束时批量落盘。批量落盘省下的那点开销，往往就是重复处理的来源。",{"type":31,"level":21,"children":751},[752],{"text":753,"type":29},"重试前如何核对目标端处理结果和代理会话",{"type":25,"children":755},[756,758,763],{"text":757,"type":29},"切换出口后核对业务状态，可参考",{"text":759,"type":29,"marks":760},"切换代理 IP 出口后如何确认请求与业务状态没有回归",[761],{"href":762,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fproxy-egress-switch-regression-testing",{"text":764,"type":29},"。代理连接或出口会话变化会影响传输与目标上下文，但业务回执应按稳定业务 ID、请求 ID及原幂等键关联。连接失效后仍可通过服务端状态查询对账，不能根据代理会话是否存活判断回执归属。",{"type":31,"level":134,"children":766},[767],{"text":768,"type":29},"查询接口、列表回查、计数和业务日志各适合何时使用",{"type":25,"children":770},[771],{"text":772,"type":29},"可按接口能力选择以下核对方式：",{"type":90,"format":91,"children":774},[775,783,791,799],{"type":94,"children":776},[777,781],{"text":778,"type":29,"marks":779},"查询接口",[780],{"type":236},{"text":782,"type":29},"：按去重键查单条状态，适合恢复前逐条确认。",{"type":94,"children":784},[785,789],{"text":786,"type":29,"marks":787},"列表回查",[788],{"type":236},{"text":790,"type":29},"：按时间窗或分页拉取目标端记录，与本地清单比对，适合没有单条查询的接口。",{"type":94,"children":792},[793,797],{"text":794,"type":29,"marks":795},"计数对账",[796],{"type":236},{"text":798,"type":29},"：目标端总数对比本地已完成数，前提是统计范围、时间窗、软删除、分页与异步落库的口径一致。它只能提示\"可能有差异\"，不能直接推断漏项，也不能定位到哪一条。",{"type":94,"children":800},[801,805],{"text":802,"type":29,"marks":803},"业务日志",[804],{"type":236},{"text":806,"type":29},"：目标端或下游的操作日志，按时间和去重键匹配，通常作为兜底。",{"type":25,"children":808},[809,811,816],{"text":810,"type":29},"目标端写入可能有延迟，刚写完查不到时，应按接口约定等待后再查。查询本身也可能触发限流，批量核对要控制频率。限流后的暂停与恢复思路，可参考",{"text":812,"type":29,"marks":813},"采集任务遇到 429 后如何暂停和恢复",[814],{"href":815,"type":52},"https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002F429-how-long-before-next-request",{"text":76,"type":29},{"type":31,"level":134,"children":818},[819],{"text":820,"type":29},"没有查询接口时，如何降低重复处理风险",{"type":25,"children":822},[823],{"text":824,"type":29},"此时只能降级处理。目标端明确支持并保证该键语义时，才按最小粒度重放、复用同一个键，同时把这条标成\"可能重复\"，任务结束后统一对账。目标端不支持时，客户端带键不会让它自动去重，应保持\"结果未知\"，转人工或等可核实的回执。即便目标端支持，这条路径也只能降低重复概率，不能证明不重复，记录里要写明这一点，不要承诺\"绝不重复\"。",{"type":31,"level":21,"children":826},[827],{"text":828,"type":29},"发现重复数据后，如何对账并处理差异",{"type":25,"children":830},[831],{"text":832,"type":29},"重复一旦发生，顺序是\"先定位、再收敛、最后记录\"，不要边跑边改。",{"type":25,"children":834},[835],{"text":836,"type":29},"定位靠对账表，至少记六项：去重键、本地状态、目标端状态、差异类型、处理动作、处理时间。对账频率按任务量定，日终一次通常够用；数据量大、单条影响大时，改成每批一次。",{"type":25,"children":838},[839],{"text":840,"type":29},"对账结果只有三种，处理方式不同：",{"type":121,"children":842},[843],{"text":844,"type":29},"| 差异类型 | 表现 | 处理方式 |\n| --- | --- | --- |\n| 漏处理候选 | 本地有、目标端暂未查到 | 先按接口一致性约定等待并查询权威状态；确认未执行，或服务端仍有覆盖本次意图的有效幂等契约后，才可补跑 |\n| 重复处理 | 目标端同一键多条 | 保留一条，其余按业务规则撤销或标记 |\n| 状态不一致 | 两边都有但字段不同 | 按业务权威数据源、事件时间和一致性规则裁决；确认目标端记录不是暂态或延迟状态后，再回写本地 |",{"type":25,"children":846},[847],{"text":848,"type":29},"收敛动作要区分能不能自动做：补跑和回写状态可以自动；撤销、删除、退款这类有外部影响的操作，一律转人工。不要写\"发现重复就自动删除\"的逻辑，删错一条的代价通常比多留一条高。",{"type":25,"children":850},[851],{"text":852,"type":29},"补救完成后，把这次的差异类型和处理方式记录下来。如果同一类差异反复出现，说明状态机或键的粒度有问题，要回去改设计，而不是每次都靠对账收尾。",{"type":31,"level":21,"children":854},[855],{"text":132,"type":29},{"type":31,"level":134,"children":857},[858],{"text":859,"type":29},"代理 IP 重连之后，幂等键应该存在哪里？",{"type":25,"children":861},[862],{"text":863,"type":29},"与业务数据同一事务写入。分开写会出现\"数据落了、键没落\"，恢复时仍认不出。",{"type":31,"level":134,"children":865},[866],{"text":867,"type":29},"任务重跑会覆盖上次结果吗？",{"type":25,"children":869},[870],{"text":871,"type":29},"不能只按覆盖式或追加式判断。先核对版本冲突、计费、通知等副作用及服务端幂等约定；只有确认重放安全后才重跑。追加写也可能由唯一约束去重，不能一概断言会翻倍。",{"type":31,"level":134,"children":873},[874],{"text":875,"type":29},"状态一直停在\"处理中\"，能当失败重跑吗？",{"type":25,"children":877},[878],{"text":879,"type":29},"不能。处理中与结果未知都要先核对目标端，直接重置为待处理就是重复来源。",{"type":31,"level":134,"children":881},[882],{"text":883,"type":29},"两个工作进程同时拿到同一批数据怎么办？",{"type":25,"children":885},[886],{"text":887,"type":29},"用原子抢占：待处理→处理中必须一步完成。否则两边都以为自己是第一个。",{"type":25,"children":889},[890,891,894],{"text":392,"type":29},{"text":394,"type":29,"marks":892},[893],{"href":397,"type":52},{"text":76,"type":29},[896],{"source":6,"id":7,"documentId":8,"translationKey":8,"locale":9,"slug":10,"path":11,"_path":11,"title":12,"description":13,"excerpt":13,"image":14,"publishedAt":15,"updatedAt":16,"author":17,"tags":897,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":898,"bodyHtml":154},[],[899,902,905,908,911,922,925,932,935,938,941,952,955,962,965,968,971,974,977,980,983],{"type":25,"children":900},[901],{"text":28,"type":29},{"type":31,"level":21,"children":903},[904],{"text":34,"type":29},{"type":25,"children":906},[907],{"text":38,"type":29},{"type":31,"level":21,"children":909},[910],{"text":42,"type":29},{"type":25,"children":912},[913,914,917,918,921],{"text":46,"type":29},{"text":48,"type":29,"marks":915},[916],{"href":51,"type":52},{"text":54,"type":29},{"text":56,"type":29,"marks":919},[920],{"href":59,"type":52},{"text":61,"type":29},{"type":31,"level":21,"children":923},[924],{"text":65,"type":29},{"type":25,"children":926},[927,928,931],{"text":69,"type":29},{"text":71,"type":29,"marks":929},[930],{"href":74,"type":52},{"text":76,"type":29},{"type":31,"level":21,"children":933},[934],{"text":80,"type":29},{"type":25,"children":936},[937],{"text":84,"type":29},{"type":25,"children":939},[940],{"text":88,"type":29},{"type":90,"format":91,"children":942},[943,946,949],{"type":94,"children":944},[945],{"text":97,"type":29},{"type":94,"children":947},[948],{"text":101,"type":29},{"type":94,"children":950},[951],{"text":105,"type":29},{"type":31,"level":21,"children":953},[954],{"text":109,"type":29},{"type":25,"children":956},[957,958,961],{"text":113,"type":29},{"text":115,"type":29,"marks":959},[960],{"href":118,"type":52},{"text":76,"type":29},{"type":121,"children":963},[964],{"text":124,"type":29},{"type":25,"children":966},[967],{"text":128,"type":29},{"type":31,"level":21,"children":969},[970],{"text":132,"type":29},{"type":31,"level":134,"children":972},[973],{"text":137,"type":29},{"type":25,"children":975},[976],{"text":141,"type":29},{"type":31,"level":134,"children":978},[979],{"text":145,"type":29},{"type":25,"children":981},[982],{"text":149,"type":29},{"type":25,"children":984},[985],{"text":153,"type":29},null,[],[]]