Cloudflare Tunnel v2026.11.0起默认启用URL路径规范化
Cloudflare Tunnel, Cloudflare Tunnel for SASE - Cloudflare Tunnel extends URL normalization
涉及核心代理工具 cloudflared 的行为变更与弃用，2027年2月8日强制生效。若你的路由规则包含分号参数且依赖 Access 验证，必须在此之前完成测试与迁移，否则可能面临路由失效或安全策略异常。
Starting from version 2026.11.0, Cloudflare Tunnel extends the URL normalization introduced in 2026.10.0. Normalization now handles semicolon-delimited path parameters before matching ingress rules. This improves security for tunnels with rules that require Cloudflare Access validation. The URL path sent to your origin stays the same.
从版本 2026.11.0 开始，Cloudflare Tunnel 扩展了 2026.10.0 中引入的 URL 规范化功能。规范化现在会在匹配入口规则之前处理以分号分隔的路径参数。这提高了需要 Cloudflare Access 验证的隧道的安全性。发送到您源站的 URL 路径保持不变。
Starting 2027-02-08, new cloudflared releases will turn on URL normalization by default. This replaces the previously announced date of 2027-01-25, giving you time to test the updated behavior. Upgrade to version 2026.11.0 or later and test your path-based routing before that date, including rules that match paths containing semicolons. Configurations without rules requiring Access validation are unaffected.
自 2027-02-08 起，新的 cloudflared 发行版将默认启用 URL 规范化。这取代了此前宣布的 2027-01-25 日期，为您留出时间测试更新后的行为。在此日期之前，请升级到版本 2026.11.0 或更高版本，并测试您的基于路径的路由，包括匹配包含分号的路径的规则。不需要 Access 验证的规则配置不受影响。
This setting is currently off by default. To turn it on, run:
此设置当前默认关闭。要启用它，请运行：
cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>Alternatively, set TUNNEL_DISABLE_PATH_NORMALIZATION=false on each cloudflared replica and restart it.
或者，在每个 cloudflared 副本上设置 TUNNEL_DISABLE_PATH_NORMALIZATION=false 并重启它。
For more information, refer to ingress matching and Access validation at the origin.
更多信息，请参阅入口匹配和源站上的 Access 验证。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力