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