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