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