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