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