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