Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved app-proxy doesn't do paths?

    Support
    app proxy
    3
    8
    94
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • robi
      robi last edited by girish

      Is there a good reason this doesn't work?
      b0469329-39b8-4e43-a273-48de799aabdb-image.png

      Life of Advanced Technology

      1 Reply Last reply Reply Quote 0
      • nebulon
        nebulon Staff last edited by

        Is there a specific use-case to support this?

        robi 1 Reply Last reply Reply Quote 0
        • girish
          girish Staff last edited by nebulon

          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.

          1 Reply Last reply Reply Quote 0
          • robi
            robi @nebulon last edited by

            @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.

            Life of Advanced Technology

            nebulon 1 Reply Last reply Reply Quote 0
            • nebulon
              nebulon Staff @robi last edited by

              @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 1 Reply Last reply Reply Quote 0
              • robi
                robi @nebulon last edited by 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)

                Life of Advanced Technology

                nebulon 1 Reply Last reply Reply Quote 0
                • nebulon
                  nebulon Staff @robi last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • Referenced by  robi robi 
                  • Topic has been marked as a question  girish girish 
                  • Topic has been marked as solved  girish girish 
                  • girish
                    girish Staff last edited by

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

                    1 Reply Last reply Reply Quote 1
                    • First post
                      Last post
                    Powered by NodeBB