Breaking change
Cloudflare: Cloudflare Tunnel, Cloudflare Tunnel for SASE - Cloudflare Tunnel extends URL normalization
What changed
- 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.
- The URL path sent to your origin is unchanged.
- Beginning 2027-02-08, new cloudflared releases enable URL normalization by default.
- This default date replaces the previously announced date of 2027-01-25.
- The setting is currently off by default.
Who it affects
- Tunnels with rules that require Cloudflare Access validation are affected, improving their security.
- Configurations without rules requiring Access validation are unaffected.
What to do now
- Upgrade to version 2026.11.0 or later and test path-based routing before that date, including rules matching paths containing semicolons.
- To enable the setting, run the cloudflared tunnel command with path normalization disabling set to false.
- Alternatively, set TUNNEL_DISABLE_PATH_NORMALIZATION=false on each cloudflared replica and restart it.
Your users need to hear about your changes too
FoxPlug writes the changelog entry, the heads-up email draft and the social posts from what you ship.
Try it on your projectYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries