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