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