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