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