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