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