Skip to content

Cloudflare Tunnel will normalise semicolon paths by default from February

cloudflared 2026.11.0 can now strip semicolon-delimited path parameters before matching ingress rules. The old behaviour becomes default off from 8 February 2027.

Cloudflare Tunnel’s client, cloudflared, now normalises semicolon-delimited path parameters, such as /path;param=value, before matching them against ingress rules. The feature ships in version 2026.11.0 and is off by default for now.

It matters for tunnels whose ingress rules lean on Cloudflare Access for authentication: an unnormalised path can otherwise route around the rule that is meant to require a login. The path sent on to your origin server is unchanged, this only affects how cloudflared matches it against your rules. Cloudflare set 8 February 2027 as the date new cloudflared releases switch this on by default, pushed back from an earlier 25 January target. Until then, turn it on with cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>, or the equivalent TUNNEL_DISABLE_PATH_NORMALIZATION=false environment variable.

cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>

Why it matters: if you run Cloudflare Tunnel with Access-gated ingress rules, test your path-based routing against semicolon parameters now, before the default flips in February. Anything that quietly starts matching differently is easier to catch on your own terms than Cloudflare’s.

Share

Related reading

More from The Wire

All briefs