🐛 Public Hostnames "Path" is appended to Service URL

[michaelweinold]

Opening this as a cloudflared issue at the suggestion of @ranbel. See also: cloudflare/cloudflare-docs#7264

Describe the bug

The Public Hostname Page for a Cloudflare Tunnel has three fields:

(optional) Subdomain	(required) Domain	(optional) Path

As the documentation clearly states, this can be used to expose http resources like so:

subdomain.domain.com >> http://localhost:1234

However, it seems that the beheviour is currently such that instead of:

subdomain.domain.com/path1 >> http://localhost:1234
subdomain.domain.com/path2 >> http://localhost:5678

we get:

subdomain.domain.com/path1 >> http://localhost:1234/path1
subdomain.domain.com/path1 >> http://localhost:1234/path2

To Reproduce
Steps to reproduce the behavior:

1. Follow the Cloudflared documentation to expose any HTTP resources to the Internet via a public hostname.

Expected behavior

subdomain.domain.com/path1 >> http://localhost:1234
subdomain.domain.com/path2 >> http://localhost:5678

Environment and versions

• OS: macOS
• Architecture: ARM
• Version: 1429-9b8a53343597

Logs and errors
N/A

Additional context
N/A

[chulkilee]

This is very cumbersome - we may put a component rewriting the path in front of service, but it would be ideal if cloudflared can do this. This would be a breaking change so probably needs a config at each public hostname level.

[SeeleVolleri]

I was wondering why application always returned 404 until I see this issue.

The reason I use the feature was thinking of minimum exposure of control panel an such, only redirect to real panel only if typed right path, and I don't really want another proxy to do rewrite job.

If possible, please add a option at path that indicates only allow specified route, or redirect to specified route.

[sadorowo]

i was thinking why I was getting 404s, until i finally found this issue. I want to avoid any kind of reverse proxies just for such as simple behavior as that.

[WolfganP]

Same here, it took a while to figure out what was happening with multiple services running erratically under the same connector...

[ThatIsAPseudo]

I keep forgetting this weird behaviour, every time it takes me some time to understand what isn't working... Is this issue currently investigated ?