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