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