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