[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"blog-strapi-article:zh:caddy-nginx-websocket-proxy-configuration":3,"blog-article:\u002Fblog\u002Fcaddy-nginx-websocket-proxy-configuration":635,"blog-related:\u002Fblog\u002Fcaddy-nginx-websocket-proxy-configuration":636,"blog-translations:\u002Fblog\u002Fcaddy-nginx-websocket-proxy-configuration":637},{"available":4,"article":5,"relatedArticles":163,"translations":532},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":162},"strapi",3495,"s72p6uye6i8b0jr2mlb0l97b","zh","caddy-nginx-websocket-proxy-configuration","\u002Fblog\u002Fcaddy-nginx-websocket-proxy-configuration","Caddy 与 Nginx 的 WebSocket 代理配置有什么区别：升级头与超时","对比 Caddy 与 Nginx 的 WebSocket 反向代理配置，说明 HTTP\u002F1.1 Upgrade、空闲超时和版本差异，并给出断连排查方法。","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_caddy_nginx_websocket_cover_7b9d0db2cc.webp","2026-10-21T08:23:34.532Z","2026-10-21T08:23:34.515Z","Global Proxies Team",[],false,0,4,"blocks",[24,30,34,40,44,48,52,56,60,64,68,72,76,81,85,89,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158],{"type":25,"children":26},"paragraph",[27],{"text":28,"type":29},"两者都能代理 WebSocket。本文示例采用传统 HTTP\u002F1.1 Upgrade：Nginx 需要正确转发升级头；Caddy 的 `reverse_proxy` 会处理升级。连接建立后是否断开，还要看读空闲超时、连接总时长和中间层策略。下面给出配置示例与版本边界。","text",{"type":25,"children":31},[32],{"text":33,"type":29},"排查时先看握手是否成功，再看连接建立后的断开时间和各层日志。客户端出网代理的协议选择见[HTTP、HTTPS、SOCKS5 代理怎么选](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fhttp-https-socks5-proxy-selection)。",{"type":35,"level":36,"children":37},"heading",2,[38],{"text":39,"type":29},"Nginx 如何配置 WebSocket 升级头和读超时",{"type":25,"children":41},[42],{"text":43,"type":29},"```nginx\nlocation \u002Fws\u002F {\nproxy_pass http:\u002F\u002F127.0.0.1:8080;\nproxy_http_version 1.1;\nproxy_set_header Upgrade $http_upgrade;\nproxy_set_header Connection \"upgrade\";\nproxy_read_timeout 3600s;\nproxy_buffering off;\n}\n```",{"type":25,"children":45},[46],{"text":47,"type":29},"`Upgrade` 与 `Connection` 用于传统 HTTP\u002F1.1 握手；`proxy_read_timeout` 控制两次上游读取之间允许的空闲时间，长空闲连接应按应用心跳和实际链路设置。Nginx 官方文档对 HTTP\u002F1.1 默认值有版本说明：1.29.7 之前需显式设置；示例保留显式配置以兼容较旧版本。升级后的连接按隧道工作，不能把普通 HTTP 响应缓冲直接当作握手条件。长连接保活见[WebSocket 代理如何保持长连接](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fwebsocket-proxy-long-lived-connection)。",{"type":35,"level":36,"children":49},[50],{"text":51,"type":29},"Caddy 如何用 reverse_proxy 转发 WebSocket",{"type":25,"children":53},[54],{"text":55,"type":29},"```caddyfile\nexample.com {\nreverse_proxy 127.0.0.1:8080\n}\n```",{"type":25,"children":57},[58],{"text":59,"type":29},"这就够了。Caddy 会在转发时处理升级，不需要手写 `Upgrade` 和 `Connection`。只有业务需要限制整条流连接的最长存活时间时才设置 `stream_timeout`；它不是空闲超时，达到上限时活动连接也会关闭。外层 `example.com { }` 与上面相同：",{"type":25,"children":61},[62],{"text":63,"type":29},"```caddyfile\nreverse_proxy 127.0.0.1:8080 {\nstream_timeout 24h\n}\n```",{"type":25,"children":65},[66],{"text":67,"type":29},"`stream_timeout` 限制流连接总时长，默认不设此上限；不要用它代替心跳或空闲检测。配置重载时的 `stream_close_delay` 是另一项行为。`transport http` 的读写超时也应按对应文档和应用行为核实。配置项见 [Caddy reverse_proxy 文档](https:\u002F\u002Fcaddyserver.com\u002Fdocs\u002Fcaddyfile\u002Fdirectives\u002Freverse_proxy)。",{"type":25,"children":69},[70],{"text":71,"type":29},"代理本身的主机、端口和鉴权写法，见帮助中心的[代理设置](https:\u002F\u002Fhelp.quanqiudaili.com\u002Fdocs\u002Fproxy-Settings)。",{"type":35,"level":36,"children":73},[74],{"text":75,"type":29},"升级头、空闲超时和响应缓冲会怎样影响连接",{"type":77,"children":78},"code",[79],{"text":80,"type":29},"| 对比项 | Nginx | Caddy | 实际影响 |\n|---|---|---|---|\n| HTTP\u002F1.1 Upgrade | 通常需显式转发升级头；HTTP\u002F1.1 默认值受版本影响 | `reverse_proxy` 处理升级 | 配置与版本不匹配可能导致握手失败 |\n| 空闲读超时 | `proxy_read_timeout` 控制上游读取空闲间隔 | 依据具体传输配置 | 按心跳和链路实际空闲策略判断 |\n| 流连接总时长 | 由具体配置决定 | `stream_timeout` 可设总时长上限 | 到时会关闭活动连接 |\n| 响应缓冲 | Upgrade 后是双向隧道；按实际数据路径排查 | 流式转发 | 不作为握手成功的必备条件 |\n| 证书 | 需另配 certbot | 自动申请续期 | 部署步骤数量不同 |\n| HTTP\u002F2 | 取决于客户端与服务器实现 | 取决于实现 | RFC 8441 定义扩展 CONNECT，支持情况需逐端核实 |",{"type":25,"children":82},[83],{"text":84,"type":29},"若使用传统 Upgrade，按 HTTP\u002F1.1 握手流程排查；HTTP\u002F2 扩展 CONNECT 是否可用取决于客户端、代理和上游实现。若只有特定目标失败，比较该目标的响应和代理日志，不要直接归因于出口。",{"type":35,"level":36,"children":86},[87],{"text":88,"type":29},"如何设置 WebSocket 保活间隔并定位断连",{"type":35,"level":90,"children":91},3,[92],{"text":93,"type":29},"按链路最短空闲超时设置 ping 间隔",{"type":25,"children":95},[96],{"text":97,"type":29},"链路上任一层的空闲策略都可能关闭连接，实际时限需查对应 CDN、负载均衡和应用配置，并用边缘及后端日志测量。不要把未经核实的固定秒数当作通用默认值。应用层心跳间隔应依据实测到的最短空闲时限设置，并留出网络抖动余量。",{"type":35,"level":90,"children":99},[100],{"text":101,"type":29},"握手失败或连接中断时按四步排查",{"type":25,"children":103},[104],{"text":105,"type":29},"排障按这个顺序走，不要跳步：",{"type":25,"children":107},[108],{"text":109,"type":29},"1. `curl -i -N -H \"Connection: Upgrade\" -H \"Upgrade: websocket\" -H \"Sec-WebSocket-Version: 13\" -H \"Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw==\" http:\u002F\u002F你的域名\u002Fws\u002F`，看是否返回 `101 Switching Protocols`\n2. 没有 101 就查 Nginx 的头和 `proxy_pass` 路径\n3. 有 101 但很快断，记录断开间隔并对照各层实际超时配置与日志\n4. 断得没有规律，结合代理、CDN 和后端日志检查连接限制或异常关闭原因",{"type":35,"level":90,"children":111},[112],{"text":113,"type":29},"根据 400、502、504 和固定时长断连定位故障层",{"type":25,"children":115},[116],{"text":117,"type":29},"出现下面这些现象时，先查对应的一层，不要先改代理：",{"type":77,"children":119},[120],{"text":121,"type":29},"| 现象 | 先查哪一层 | 判断动作 |\n|---|---|---|\n| 握手返回 400 或 426 | Nginx 升级头 | 核对 `Upgrade`、`Connection` 和 HTTP\u002F1.1 |\n| 返回 502 | 后端 | 后端进程、端口、路径是否与 `proxy_pass` 一致 |\n| 返回 504 | Nginx 读超时 | 看后端处理耗时，再调 `proxy_read_timeout` |\n| 101 之后 60 秒整断 | Nginx | `proxy_read_timeout` 仍是默认值 |\n| 101 后固定时长断开 | CDN、负载均衡或应用 | 对照该层配置及日志确认空闲策略 |\n| 消息延迟或成批到达 | 应用写入、代理或中间层 | 检查数据流和缓冲行为，不据此判断握手失败 |",{"type":25,"children":123},[124],{"text":125,"type":29},"超时、连接被拒和 TLS 证书错误是三组不同原因：超时多半卡在链路或上游，连接被拒说明端口那头没在听，证书错误说明中间有人在拦截或替换证书。先按 curl 报出的类型分开，再决定动哪一端。",{"type":35,"level":36,"children":127},[128],{"text":129,"type":29},"FAQ",{"type":35,"level":90,"children":131},[132],{"text":133,"type":29},"Caddy 还要不要显式写 Upgrade 头",{"type":25,"children":135},[136],{"text":137,"type":29},"不用。v2 的 reverse_proxy 会自动处理升级，手写反而可能覆盖掉它自己的逻辑。只有当你需要改写头内容时才用 `header_up`。",{"type":35,"level":90,"children":139},[140],{"text":141,"type":29},"Nginx 报 502 和 504 分别查什么",{"type":25,"children":143},[144],{"text":145,"type":29},"502 是后端拒绝或崩溃，查后端进程和端口；504 是后端在超时内没响应，查 `proxy_read_timeout` 和后端处理耗时。两者都不指向代理 IP 本身。",{"type":35,"level":90,"children":147},[148],{"text":149,"type":29},"HTTP\u002F2 下 WebSocket 还能用吗",{"type":25,"children":151},[152],{"text":153,"type":29},"RFC 8441 定义了 HTTP\u002F2 的扩展 CONNECT；是否可用取决于客户端、代理及服务端实现。本文配置示例采用传统 HTTP\u002F1.1 Upgrade，部署时应核实整条链路支持的方式。",{"type":25,"children":155},[156],{"text":157,"type":29},"---",{"type":25,"children":159},[160],{"text":161,"type":29},"如果长连接主要面向需要稳定出口的业务后台，用[静态住宅代理 IP](https:\u002F\u002Fwww.quanqiudaili.com\u002Fproduct\u002Fstatic-residential-standard) 比频繁更换出口更省事，出口固定之后，超时和缓冲问题也更容易复现。","",[164,292,412],{"source":6,"id":165,"documentId":166,"translationKey":166,"locale":9,"slug":167,"path":168,"_path":168,"title":169,"description":170,"excerpt":171,"image":172,"publishedAt":173,"updatedAt":174,"author":17,"tags":175,"featured":19,"sortOrder":20,"readingTime":90,"bodyType":22,"bodyBlocks":176,"bodyHtml":162},3656,"ekifxujrbn3ntaau1tjbmimb","saas-regional-issue-ticket-reproduction-fields","\u002Fblog\u002Fsaas-regional-issue-ticket-reproduction-fields","SaaS 地区问题工单模板怎么写？快速复现字段清单","SaaS 地区问题工单应记录复现步骤、期望与实际、地区和版本、发生时间、请求标识及脱敏证据，帮助团队判断问题层级并复现现象。","SaaS 地区问题工单应记录复现步骤、期望与实际、地区和版本、发生时间、请求标识及脱敏证据，帮助团队判断问题层级并复现现象。\n\n","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_saas_cover_c45f338688.webp","2026-10-26T09:51:28.641Z","2026-10-26T09:51:28.627Z",[],[177,181,185,189,193,197,201,205,209,213,217,221,225,229,233,237,241,245,249,253,257,260,264,268,272,276,280,284,288],{"type":25,"children":178},[179],{"text":180,"type":29},"工单先描述现象和复现条件，再补期望结果、实际结果、版本、地区与请求标识。字段齐全能减少补充沟通，但最终分派仍应由团队依据证据判断；下文提供可按需采用的模板。本文把通用缺陷报告的字段细化到地区问题，不另建一套通用 QA 报告规范。",{"type":35,"level":36,"children":182},[183],{"text":184,"type":29},"先把现象写到可以复现",{"type":25,"children":186},[187],{"text":188,"type":29},"如果工单只写“某地区打不开”，接单团队通常还需要追问复现条件。先描述请求发生在哪个环节，再补足版本、地区、期望和实际结果，能帮助团队更快判断由谁继续处理。",{"type":25,"children":190},[191],{"text":192,"type":29},"例如，“某地区打不开”可以补成：“在测试地区 A 使用版本 2.4.1 提交注册，页面返回 500；尝试 10 次复现 9 次，Trace ID 已附，预期应进入邮箱验证。”这是虚构格式示例，实际工单应填写真实测试记录并脱敏。",{"type":35,"level":90,"children":194},[195],{"text":196,"type":29},"先说明问题可能属于网络、配置、数据还是产品逻辑",{"type":25,"children":198},[199],{"text":200,"type":29},"网络、配置、数据或产品问题可作为初步分诊方向，证据不足时标记“待确认”。分诊层级能帮助确定初始接单团队，但响应时限应以团队公开的支持流程为准。若问题发生在注册限制或提示环节，可参考[多地区注册测试](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fsaas-multi-region-signup-restriction-testing)补充账户状态和规则命中信息。",{"type":35,"level":36,"children":202},[203],{"text":204,"type":29},"一份能直接派单的工单长这样",{"type":25,"children":206},[207],{"text":208,"type":29},"下面给出一组字段示例。各团队可按内部流程调整必填项，并避免把敏感凭证写入工单。",{"type":77,"children":210},[211],{"text":212,"type":29},"| 字段 | 是否必填 | 填写示例 | 缺了会怎样 |\n|---|---|---|---|\n| 分诊层级 | 必填 | 疑似应用层（接口 500） | 初始接单团队要重新判断 |\n| 复现步骤（测试步骤） | 必填 | 1 登录 2 选地区 3 提交 4 报错 | 处理人无法独立重现 |\n| 期望与实际 | 必填 | 期望创建成功，实际提示地区不可用 | 无法判断是否算缺陷 |\n| 出现频率 | 必填 | 记录已知复现次数、尝试次数及观察窗口；暂时无法统计时注明“总尝试次数未知” | 偶发问题难定级 |\n| 首次出现时间 | 必填 | 记录日期、时间与 UTC 偏移 | 难以与发布记录对齐 |\n| 请求 ID（Trace ID） | 有则填写 | 填写 Trace ID；没有时记录可定位的请求时间 | 无法关联日志；没有 Trace ID 时可用时间、入口等可关联信息并注明 |\n| 环境\u002F版本 | 必填 | 产品版本、客户端版本、测试地区 | 无法确认复现条件 |\n| 出口与网络 | 视问题填写 | 测试地区、网络类型及检测时间 | — |\n| 脱敏状态 | 提交前必须确认 | 已移除手机号与令牌 | 安全会拦下工单并暂停流转 |\n| 附件 | 选填 | 截图 2 张，含提示原文 | — |\n| 影响范围 | 选填 | 单账户或整地区 | — |",{"type":25,"children":214},[215],{"text":216,"type":29},"API 延迟类问题还应附上采样窗口、分位数和样本量；具体口径可对照[地区延迟基线](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fsaas-api-region-latency-baseline)填写。",{"type":25,"children":218},[219],{"text":220,"type":29},"可直接复制的工单块（尖括号为占位，按团队必填项删减）：",{"type":25,"children":222},[223],{"text":224,"type":29},"标题：\u003C地区> + \u003C功能入口> + \u003C现象> + \u003C版本>\n环境\u002F版本：产品 \u003Cx.y.z>；客户端 \u003C平台与版本>；测试地区 \u003C地区>；入口 \u003C页面或 URL>\n时间与时区：\u003CYYYY-MM-DD HH:MM（UTC±x）>；首次出现 \u003C时间>；最近一次 \u003C时间>\n前置状态：\u003C账户状态、权限、功能开关、缓存状态>\n测试步骤：1) \u003C步骤> 2) \u003C步骤> 3) \u003C步骤>\n期望：\u003C应有的结果>\n实际：\u003C实际结果与提示原文>\n次数与窗口：尝试 \u003Cn 或未知> 次，复现 \u003Cm 或未知> 次，观察 \u003C窗口>；总次数未知时注明“总尝试次数未知”\n请求 ID（Trace ID）：\u003C值>；服务端返回码：\u003Ccode>\n证据脱敏确认：已移除手机号、邮箱、令牌、Cookie 与精确地址\n影响范围：\u003C单账户、单地区或多地区>\n待确认项：\u003C怀疑方向，待验证>",{"type":35,"level":90,"children":226},[227],{"text":228,"type":29},"时间戳同时记录日期、时间和 UTC 偏移",{"type":25,"children":230},[231],{"text":232,"type":29},"\"昨天下午\"这类描述无法与日志对齐。统一写成本地时间加 UTC 偏移，例如 14:05（UTC+8），并保留原始时区，方便不同团队对齐请求记录。出口或网络信息只在与问题相关时填写，并注明采集方式和时间。",{"type":35,"level":36,"children":234},[235],{"text":236,"type":29},"缺项会被退回到哪一步",{"type":25,"children":238},[239],{"text":240,"type":29},"缺项后果已并入字段表的最后一列：按团队已确认的必填条件补齐字段；没有 Trace ID 时，可提供带时区的精确请求时间、入口及其他可关联信息，并说明暂时无法取得请求标识。观察项可记录已知次数，并注明“总尝试次数未知”。涉及敏感信息时，按组织安全流程处理。",{"type":35,"level":36,"children":242},[243],{"text":244,"type":29},"提交前核对工单信息",{"type":25,"children":246},[247],{"text":248,"type":29},"提交前检查复现步骤是否可独立执行、期望与实际是否分开描述、时间是否带时区、请求标识能否关联日志，以及附件是否已脱敏。分诊不确定时写“待确认”，不要为了填字段而猜根因；若发现敏感信息，按组织安全流程暂停流转并清理附件。",{"type":35,"level":90,"children":250},[251],{"text":252,"type":29},"偶发问题注明尝试次数和观察时间范围",{"type":25,"children":254},[255],{"text":256,"type":29},"“偶发”不足以复现。记录已知的尝试次数、复现次数和观察窗口；暂时无法统计总次数时，写明采样条件、已观察到的次数，并注明“总尝试次数未知”，避免把有限观察当成稳定结论。",{"type":35,"level":36,"children":258},[259],{"text":129,"type":29},{"type":35,"level":90,"children":261},[262],{"text":263,"type":29},"没有 Trace ID，还能提交工单吗？",{"type":25,"children":265},[266],{"text":267,"type":29},"可以。有 Trace ID 时填写；没有时，提供带时区的精确请求时间、入口、复现步骤及环境，并说明暂时无法取得请求标识。是否必填或退回按团队已确认的流程处理。",{"type":35,"level":90,"children":269},[270],{"text":271,"type":29},"暂时无法稳定复现，要不要提交？",{"type":25,"children":273},[274],{"text":275,"type":29},"可以先作为观察项提交，附已知次数、尝试次数和时间范围，后续复现时补充证据。",{"type":35,"level":90,"children":277},[278],{"text":279,"type":29},"用户截图带地区信息怎么脱敏？",{"type":25,"children":281},[282],{"text":283,"type":29},"遮挡手机号、邮箱、令牌和精确地址；保留判断问题所需的地区、语言和提示信息。",{"type":35,"level":90,"children":285},[286],{"text":287,"type":29},"日志和截图可以直接附原始文件吗？",{"type":25,"children":289},[290],{"text":291,"type":29},"先检查并移除令牌、Cookie、个人信息和精确地址，再附最小必要片段。",{"source":6,"id":293,"documentId":294,"translationKey":294,"locale":9,"slug":295,"path":296,"_path":296,"title":297,"description":298,"excerpt":299,"image":300,"publishedAt":301,"updatedAt":302,"author":17,"tags":303,"featured":19,"sortOrder":20,"readingTime":36,"bodyType":22,"bodyBlocks":304,"bodyHtml":162},3655,"gpj6mdt5zocfmuao4ii43m60","saas-api-region-latency-baseline","\u002Fblog\u002Fsaas-api-region-latency-baseline","SaaS API 地区延迟基线怎么建？请求口径与分位数","SaaS API 地区延迟基线应固定接口、请求内容、客户端和采样窗口，按地区记录 p50、p95、样本量、错误率及限流情况，并说明统计口径。","SaaS API 地区延迟基线应固定接口、请求内容、客户端和采样窗口，按地区记录 p50、p95、样本量、错误率及限流情况，并说明统计口径。\n","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_saas_api_cover_5939424cfc.webp","2026-10-26T09:51:21.825Z","2026-10-26T09:51:21.802Z",[],[305,309,313,317,321,325,329,333,337,341,345,349,353,357,361,365,369,373,377,380,384,388,392,396,400,404,408],{"type":25,"children":306},[307],{"text":308,"type":29},"报告分位数并保留样本量：p50 描述中位响应，p95 反映较慢请求，p99 仅在样本足够时参考。可比性取决于接口、客户端、负载和采样窗口一致，不存在适用于所有接口的固定请求数。本文测的是自有 API 的应用响应，不是代理网络本身的延迟与稳定性。",{"type":35,"level":36,"children":310},[311],{"text":312,"type":29},"先定分位数和判读口径",{"type":25,"children":314},[315],{"text":316,"type":29},"一个接口的平均响应时间可能掩盖尾部慢请求，因此基线通常还要报告分位数。p50 表示中位响应，p95 和 p99 描述分布尾部；同时应提供样本量、窗口、错误率和计算方法，避免只凭几个数字下结论。",{"type":77,"children":318},[319],{"text":320,"type":29},"| 指标 | 看什么 | 记录值 | 判读方式 |\n|---|---|---|---|\n| p50 | 中位响应 | 填写本轮实测值 | 按预先定义的偏差阈值复核 |\n| p95 | 较慢请求分位 | 填写本轮实测值 | 结合样本量和基线阈值复核 |\n| p99 | 尾部请求分位 | 样本足够时填写 | 结合样本量与超时策略判断 |\n| 错误率 | 按约定口径统计失败请求 | 填写本轮实测值 | 分别记录 HTTP 错误和无响应超时；分母包含约定的全部有效尝试或逻辑请求，网络失败不能因没有状态码而遗漏 |",{"type":25,"children":322},[323],{"text":324,"type":29},"示例：若 p50 稳定而 p95 明显升高、错误率变化不大，可先检查慢请求是否集中在特定时段、请求类型或下游依赖，再结合重试和连接复用记录判断。",{"type":35,"level":90,"children":326},[327],{"text":328,"type":29},"跨窗口比较时不要直接平均分位数",{"type":25,"children":330},[331],{"text":332,"type":29},"不能直接平均各窗口的分位数。总体分位数需要原始样本，或同一口径、兼容且可合并的分布数据，例如直方图或相应摘要；只有各窗口的 p95 时，不能重算总体 p95。固定窗口可用于逐窗比较，但不能恢复已经丢失的分布。使用分桶时应注明算法与精度。保留原始请求耗时是可行方案之一，并非唯一方案。",{"type":25,"children":334},[335],{"text":336,"type":29},"稳定与否要看窗口之间的波动，不看单窗口的数字。每窗口记录样本量、p95 与错误率；连续几个窗口的 p95 偏差落在预设范围内、样本量达到目标，才可宣称基线稳定，否则标为暂定并在结论中写明适用窗口。",{"type":35,"level":36,"children":338},[339],{"text":340,"type":29},"先明确延迟基线测量了哪些环节",{"type":25,"children":342},[343],{"text":344,"type":29},"基线要回答的是“用户在这个地区调用我的接口，多久能看到响应”。采样前固定测量单位和起止点：明确统计首字节（TTFB）还是完整响应体，并说明是否包含 DNS、建连、TLS、连接复用和客户端等待。它反映应用、客户端和测试网络共同作用下的观测结果；若要判断具体阶段，应在相应观测点分别采集，不能随意相加或相减来认定纯网络耗时。",{"type":35,"level":90,"children":346},[347],{"text":348,"type":29},"固定影响可比性的条件",{"type":25,"children":350},[351],{"text":352,"type":29},"固定请求体或明确区分请求类型与请求大小（含上传\u002F下载体积），记录测量起止点、是否含 DNS\u002F建连\u002FTLS、连接复用、客户端等待、采样时段、并发、客户端版本和缓存状态；不同地区使用可比的测试端与请求路径，避免把负载差异当成地区差异。",{"type":35,"level":90,"children":354},[355],{"text":356,"type":29},"分开记录预热请求与缓存命中结果",{"type":25,"children":358},[359],{"text":360,"type":29},"预热请求应单独标记，不要不加说明地混入稳态样本或直接剔除。记录剔除规则和数量；带缓存的接口还要区分命中与未命中，避免不同请求路径混在一起。测量应用响应时，应分别记录服务端处理、客户端和网络耗时。",{"type":35,"level":36,"children":362},[363],{"text":364,"type":29},"按统一口径建立并复核基线",{"type":25,"children":366},[367],{"text":368,"type":29},"1. 定接口与请求内容，记录请求体或参数，并确保测试不会修改真实用户数据。产出：接口与请求说明。\n2. 定测试地区与发起端，尽量保持客户端、版本和负载可比。产出：地区与客户端清单。\n3. 按目标分位数和流量波动确定采样量，记录预热请求及剔除理由。产出：可复核的原始样本。\n4. 按固定算法计算 p50、p95、适用时的 p99、错误率与限流占比。产出：一期统计结果。\n5. 在可比窗口复测，并根据业务周期评估基线稳定性。产出：注明适用范围和限制的基线。若这套基线用于地区发布观测，可将窗口和分组口径接入[地区灰度验证](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fsaas-regional-canary-release-rollback-criteria)，但仍需单独定义发布动作和回滚条件。",{"type":35,"level":90,"children":370},[371],{"text":372,"type":29},"对照服务端、客户端和网络指标分析波动",{"type":25,"children":374},[375],{"text":376,"type":29},"延迟波动可能来自服务端排队、网络、客户端负载、缓存或重试。按一次请求尝试还是含重试的逻辑请求统计应预先定义；成功耗时、HTTP 错误和无响应超时分别记录。先按地区和版本拆分数据，再结合服务端监控、客户端日志和请求标识归因；地区差异不能直接等同于网络或代理差异。",{"type":35,"level":36,"children":378},[379],{"text":129,"type":29},{"type":35,"level":90,"children":381},[382],{"text":383,"type":29},"每地区多少样本才够报 p95？",{"type":25,"children":385},[386],{"text":387,"type":29},"没有通用固定值。样本不足以稳定估计 p95 时，应继续采样或把结果标为暂定。",{"type":35,"level":90,"children":389},[390],{"text":391,"type":29},"预热请求要不要计入稳态基线？",{"type":25,"children":393},[394],{"text":395,"type":29},"先按目标区分冷启动和稳态结果；若剔除预热请求，注明规则和剔除数量。",{"type":35,"level":90,"children":397},[398],{"text":399,"type":29},"被限流的请求要不要计入延迟？",{"type":25,"children":401},[402],{"text":403,"type":29},"将 429 与成功请求分开统计，并同时报告限流数量和占比。",{"type":35,"level":90,"children":405},[406],{"text":407,"type":29},"不同地区的 p95 可以直接取平均吗？",{"type":25,"children":409},[410],{"text":411,"type":29},"不建议。总体分位数需基于原始样本或兼容、可合并的分布数据重新计算；仅有各地区的 p95 无法还原总体 p95。若使用固定窗口，只能按窗口比较。",{"source":6,"id":413,"documentId":414,"translationKey":414,"locale":9,"slug":415,"path":416,"_path":416,"title":417,"description":418,"excerpt":419,"image":420,"publishedAt":421,"updatedAt":422,"author":17,"tags":423,"featured":19,"sortOrder":20,"readingTime":36,"bodyType":22,"bodyBlocks":424,"bodyHtml":162},3654,"ls62ptetizm1ge4vnl0di4nr","saas-mfa-region-compatibility-recovery-testing","\u002Fblog\u002Fsaas-mfa-region-compatibility-recovery-testing","SaaS MFA 地区兼容测试怎么做？失败排查与账户恢复","用授权测试账户按挑战类型检查地区兼容性，记录设备时间偏差、验证码通道、锁定提示与恢复结果，并结合产品策略和审计日志定位差异。","用授权测试账户按挑战类型检查地区兼容性，记录设备时间偏差、验证码通道、锁定提示与恢复结果，并结合产品策略和审计日志定位差异。\n","https:\u002F\u002Fcms.quanqiudaili.com\u002Fuploads\u002Flarge_saas_mfa_cover_0fc7feefdf.webp","2026-10-26T09:51:15.193Z","2026-10-26T09:51:15.180Z",[],[425,429,433,437,441,445,449,453,457,461,465,469,473,477,481,485,489,493,497,500,504,508,512,516,520,524,528],{"type":25,"children":426},[427],{"text":428,"type":29},"先按挑战类型核对时间、通道和账户状态，再结合服务端记录确认是否命中地区策略。本文围绕授权测试账户，验证挑战、提示、恢复与日志，不提供绕过 MFA 的方法。",{"type":35,"level":36,"children":430},[431],{"text":432,"type":29},"按现象区分时间、通道和账户问题",{"type":25,"children":434},[435],{"text":436,"type":29},"收到验证码却无法通过时，时间偏差是需要核对的条件之一；容错窗口取决于产品实现。测试前记录客户端与服务端时间差，并按产品规格覆盖窗口内外的用例。若验证码未送达，则先查发送回执和设备状态。",{"type":77,"children":438},[439],{"text":440,"type":29},"| 现象 | 更可能是 | 先做哪一步 | 判为地区问题的条件 |\n|---|---|---|---|\n| TOTP 验证失败 | 生成端与验证端时间、步长或容错窗口 | 记录两端 Unix 时间及产品配置，按窗口内外用例核验 | 需结合服务端命中的地区策略证据，不能仅凭校时后仍失败判定 |\n| 短信或邮件验证码未通过 | 生成、投递、提交时间或服务端有效期 | 记录各阶段时间、回执和挑战结果 | 需结合服务端命中的地区策略证据；原地区成功仅是线索 |\n| 推送挑战未完成 | 设备令牌、推送通道或账户状态 | 查设备令牌状态、通道结果和服务端事件 | 按产品规格和实际命中的地区策略证据判断 |\n| 连续失败后被锁 | 失败计数策略 | 按产品规定核对锁定对象和恢复路径 | 结合锁定状态、挑战类型及策略记录判断 |\n| 未收到挑战码 | 发送、投递或设备接收异常 | 查发送回执、重试记录与设备状态 | 按产品规定的通道结果和日志判断 |",{"type":25,"children":442},[443],{"text":444,"type":29},"示例：测试机与服务端存在明显时间偏差时，同一验证码可能在提交前失效。记录偏差值、挑战类型和服务端结果，校准后按相同条件复测。",{"type":35,"level":90,"children":446},[447],{"text":448,"type":29},"按产品的验证码有效窗口核对时间偏差",{"type":25,"children":450},[451],{"text":452,"type":29},"不必追求毫秒级测量，但要记录偏差方向和数值，并与产品配置的验证码有效窗口比较。自动对时或设备休眠恢复可能造成实际时钟偏差；仅改显示时区通常不会改变 Unix 时间。TOTP 应按生成端和验证端 Unix 时间、时间步长及容错窗口核验。短信\u002F邮件码应按生成、投递、提交时间和服务端有效期判断；推送挑战应检查设备令牌与通道状态。",{"type":35,"level":36,"children":454},[455],{"text":456,"type":29},"地区差异从验证码通道和额外验证策略排查",{"type":25,"children":458},[459],{"text":460,"type":29},"MFA 结果可能受时间、挑战类型、账户状态、通道和服务端策略共同影响。地区差异可从验证码通道可达性及产品是否配置额外验证两方面检查，再用服务端日志确认实际命中的规则。",{"type":35,"level":90,"children":462},[463],{"text":464,"type":29},"区分验证码未送达和产品要求额外验证",{"type":25,"children":466},[467],{"text":468,"type":29},"短信、邮件或推送通道可能出现延迟、拒收或设备令牌失效；地区策略也可能要求额外验证。结合发送回执、设备状态和服务端事件，确认失败发生在验证码校验、通道送达还是进入挑战之前。",{"type":35,"level":90,"children":470},[471],{"text":472,"type":29},"通过发送回执和服务端事件定位通道故障",{"type":25,"children":474},[475],{"text":476,"type":29},"先检查挑战是否生成、通道是否接受发送、设备是否收到，以及服务端记录的失败阶段。测试时分别记录地区配置、客户端时区与网络条件；只在产品测试方案要求时才改变网络条件。",{"type":35,"level":36,"children":478},[479],{"text":480,"type":29},"在测试账户上验证挑战、锁定和恢复流程",{"type":25,"children":482},[483],{"text":484,"type":29},"先在对照地区验证账户和挑战通道，再按测试计划逐个改变地区条件并记录服务端实际命中的策略。诊断账户按批准的失败预算测试，必须在触及锁定阈值前停止；不要用这些诊断结果声称已验证锁定。",{"type":25,"children":486},[487],{"text":488,"type":29},"锁定验收应使用专用测试账户，在隔离环境中按批准计划触发产品阈值，再核对锁定提示、恢复方式和审计记录。不要在生产账户或未授权账户上反复试码。验证码、恢复码和一次性口令不写入记录或截图，工单只写脱敏后的测试编号。",{"type":35,"level":90,"children":490},[491],{"text":492,"type":29},"恢复路径要在失败前演练",{"type":25,"children":494},[495],{"text":496,"type":29},"锁定验收应在专用测试账户和隔离环境中按批准计划触发产品阈值，核对锁定对象（账户、认证器或通道）、解锁条件、恢复码及备用方式是否可用。按产品规格检查恢复码一次消费、旧码或重新生成后的码是否失效、恢复后的会话状态及审计事件。恢复后还需检查登录状态、续期与退出，可参照[浏览器会话地区回归](https:\u002F\u002Fwww.quanqiudaili.com\u002Fblog\u002Fsaas-session-state-preference-cross-region-regression)。",{"type":35,"level":36,"children":498},[499],{"text":129,"type":29},{"type":35,"level":90,"children":501},[502],{"text":503,"type":29},"改了设备时区，就等于改变验证码时间吗？",{"type":25,"children":505},[506],{"text":507,"type":29},"不一定。时区显示与系统时钟是不同设置，需记录设备实际时间相对服务端的偏差。",{"type":35,"level":90,"children":509},[510],{"text":511,"type":29},"连续失败被锁，恢复走哪条路径？",{"type":25,"children":513},[514],{"text":515,"type":29},"按产品规格确认锁定对象和解锁条件，再使用可用的恢复码、备用验证方式或管理员支持。核对恢复码的消费与失效规则、恢复后的会话和审计记录；不要把解锁后仍失败直接归为地区问题。",{"type":35,"level":90,"children":517},[518],{"text":519,"type":29},"如何区分通道未送达和验证码校验失败？",{"type":25,"children":521},[522],{"text":523,"type":29},"看服务端事件停在哪一步：挑战是否生成、通道是否返回受理、设备是否上报接收，最后才是校验结果。日志里要有挑战 ID、通道回执状态和时间戳；只有校验环节报错，才算验证码本身失败。",{"type":35,"level":90,"children":525},[526],{"text":527,"type":29},"测试能要求临时关闭 MFA 吗，边界在哪？",{"type":25,"children":529},[530],{"text":531,"type":29},"不要为通过测试而绕过 MFA。使用专用授权账户验证完整挑战和恢复流程。",[533],{"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":534,"featured":19,"sortOrder":20,"readingTime":21,"bodyType":22,"bodyBlocks":535,"bodyHtml":162},[],[536,539,542,545,548,551,554,557,560,563,566,569,572,575,578,581,584,587,590,593,596,599,602,605,608,611,614,617,620,623,626,629,632],{"type":25,"children":537},[538],{"text":28,"type":29},{"type":25,"children":540},[541],{"text":33,"type":29},{"type":35,"level":36,"children":543},[544],{"text":39,"type":29},{"type":25,"children":546},[547],{"text":43,"type":29},{"type":25,"children":549},[550],{"text":47,"type":29},{"type":35,"level":36,"children":552},[553],{"text":51,"type":29},{"type":25,"children":555},[556],{"text":55,"type":29},{"type":25,"children":558},[559],{"text":59,"type":29},{"type":25,"children":561},[562],{"text":63,"type":29},{"type":25,"children":564},[565],{"text":67,"type":29},{"type":25,"children":567},[568],{"text":71,"type":29},{"type":35,"level":36,"children":570},[571],{"text":75,"type":29},{"type":77,"children":573},[574],{"text":80,"type":29},{"type":25,"children":576},[577],{"text":84,"type":29},{"type":35,"level":36,"children":579},[580],{"text":88,"type":29},{"type":35,"level":90,"children":582},[583],{"text":93,"type":29},{"type":25,"children":585},[586],{"text":97,"type":29},{"type":35,"level":90,"children":588},[589],{"text":101,"type":29},{"type":25,"children":591},[592],{"text":105,"type":29},{"type":25,"children":594},[595],{"text":109,"type":29},{"type":35,"level":90,"children":597},[598],{"text":113,"type":29},{"type":25,"children":600},[601],{"text":117,"type":29},{"type":77,"children":603},[604],{"text":121,"type":29},{"type":25,"children":606},[607],{"text":125,"type":29},{"type":35,"level":36,"children":609},[610],{"text":129,"type":29},{"type":35,"level":90,"children":612},[613],{"text":133,"type":29},{"type":25,"children":615},[616],{"text":137,"type":29},{"type":35,"level":90,"children":618},[619],{"text":141,"type":29},{"type":25,"children":621},[622],{"text":145,"type":29},{"type":35,"level":90,"children":624},[625],{"text":149,"type":29},{"type":25,"children":627},[628],{"text":153,"type":29},{"type":25,"children":630},[631],{"text":157,"type":29},{"type":25,"children":633},[634],{"text":161,"type":29},null,[],[]]