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