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