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