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