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