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