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