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