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