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