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