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