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