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