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