Skip to content

fix: use 'auto' as default protocol for quick tunnels#1627

Open
juliosuas wants to merge 1 commit intocloudflare:masterfrom
juliosuas:fix/quick-tunnel-default-protocol-auto
Open

fix: use 'auto' as default protocol for quick tunnels#1627
juliosuas wants to merge 1 commit intocloudflare:masterfrom
juliosuas:fix/quick-tunnel-default-protocol-auto

Conversation

@juliosuas
Copy link
Copy Markdown

Problem

Quick tunnels (cloudflared tunnel --url ...) hardcode quic as the default protocol when --protocol is not specified:

if !sc.c.IsSet(flags.Protocol) {
    _ = sc.c.Set(flags.Protocol, "quic")  // ← always QUIC
}

The official docs state that auto is the default protocol, which lets cloudflared negotiate the best available protocol.

This means users running quick tunnels in environments where QUIC is blocked (firewalls, some corporate networks) will get connection failures instead of a graceful HTTP/2 fallback.

Fix

One-line change: "quic""auto"

if !sc.c.IsSet(flags.Protocol) {
    _ = sc.c.Set(flags.Protocol, "auto")  // ← matches documented default
}

Fixes #1609.

Quick tunnel was hardcoding 'quic' as the default protocol when no
--protocol flag was specified, ignoring the documented default of 'auto'.

The Cloudflare docs state that 'auto' is the default:
https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/run-parameters/#protocol

This caused quick tunnels to always use QUIC even in environments where
HTTP/2 would be preferable or where QUIC is blocked.

Fixes cloudflare#1609.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛Quick Tunnel will ALWAYS use QUIC protocol instead of auto

1 participant