Tunnel: Clarify path forwarding and reverse proxy boundary

[hugo-vicente11]

Summary

Clarifies the architectural boundary between cloudflared (as a secure connector daemon) and local reverse proxies across Cloudflare Tunnel documentation.

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[cloudflare-docs-bot]

Review

✅ No issues found in commit 94d3564.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

_{No code review issues found.}

Conventions

_{No convention issues found.}

Style Guide Review

_{No style-guide issues found.}

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

[Copilot]

Pull request overview

This PR clarifies Cloudflare Tunnel request path behavior, emphasizing that cloudflared acts as a secure connector (not a reverse proxy) and forwards the full request path to the configured local service unless you explicitly rewrite paths at the edge or via a local reverse proxy.

Changes:

• Adds explicit “path forwarding” guidance to locally-managed tunnel configuration docs (including an example and alternatives for stripping/rewriting).
• Adds a “path routing” clarification note to the “add published application” flow.
• Updates Tunnel terminology pages to describe cloudflared as a connector daemon that does not rewrite paths.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/content/partials/cloudflare-one/tunnel/locally-managed/local-tunnel-terms.mdx	Clarifies ingress rule behavior by stating cloudflared forwards the full request path.
src/content/partials/cloudflare-one/tunnel/locally-managed/configuration-file.mdx	Adds a dedicated “Path forwarding” note describing matching vs forwarding and where to do rewrites/stripping.
src/content/partials/cloudflare-one/tunnel/add-published-application.mdx	Adds a note in the published application route steps clarifying that paths aren’t rewritten/stripped.
src/content/docs/cloudflare-one/networks/connectors/cloudflare-tunnel/get-started/tunnel-useful-terms.mdx	Adds connector framing: cloudflared as a daemon (not a reverse proxy) that doesn’t alter URI paths.

---

💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.