app-proxy doesn't do paths?

[robi]

Is there a good reason this doesn't work?

[nebulon]

Is there a specific use-case to support this?

[girish]

As a whole cloudron does not support subpaths and only subdomains. When using subpaths, one needs to also consider the security (csrf, cookies, local storage) etc . It's not solvable at a generic level and not worth the trouble.

[robi]

@nebulon Yes, considering how proxies work, even reverse proxies have the ability to take an input http request and transform it into an output request of any destination.

Hence if I want a subdomain entry point to go to a API path, that makes things easier. Besides, we do the reverse of this all the time in presenting web apps via simpler URLs from more complex paths from backend services.

It seems like really basic functionality that's missing if only (sub).domain.com to (sub).domain.com mappings are supported. Paths are a critical part of the web.

[nebulon]

@robi it seems to me that this might as well be handled in the upstream server then for the moment. Of course we can add further URL rewrite capabilities in the future, but I guess we wait a bit to collect further requirements in that area first.

[robi]

@nebulon if that's the view, then there is no need for the app-proxy rewrite, no?

Yet there is.

All these scenarios and their reverse variants are useful, including any parameteres at the end:

1. tld --> tld
2. sub --> tld
3. path --> tld
4. path --> sub
5. path --> path
6. any --> :port(/path)

[nebulon]

@robi I agree it is useful, maybe you can add this as a feature request though, as currently it is explicitly not supported.

[girish]

Feature request at https://forum.cloudron.io/topic/8487/enhance-app-proxy-app-with-path-and-port-support