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