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