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