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