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