Nginx Proxied Port request matching

njenkins

I have a question regarding the Nginx configuration which is generated by a creating a proxy port application.

I've created an "Nginx proxy port" application, attached it to a site and can see the traffic come into the rest-server I have running. The issue is the base url is being passed to the server rather than being stripped as I would like to configure. The rest-server I'm trying to configure with the proxied port uses the first portion of the request as the "user", so it see the "user" as "/<path>/<user>" rather than only "/<user>"

Site configured as follows:

<Django app> -> /
<Nginx Static Only app> -> /static/
<Nginx Proxy Port app> -> /path/

I've tried configuring the application on the site without the trailing slash, "/path" and it is added back on after updating "/path/".

Is there a method to have the proxied port direct traffic from "/path/example" to "/example", i.e. allow Nginx to replace the matching part of the request?
Is there a different application to use instead of "Nginx Proxy Port" to solve this?
Is there simply an additional location to modify the nginx.conf file I am missing?

sean

njenkins your app will need to be configured to recognize that it is running on a sub-path.

For Django apps and other uwsgi apps you can use the following instructions: Serving a Django app on a sub-path

If it's some other type of app then check its own documentation to see what the applicable configuration options are. If you're not sure, then let me know what type of app it is (ie the language and framework) and I'll try to help you sort it out.

njenkins

I'm trying to run the restic rest-server (https://github.com/restic/rest-server). If I were able to configure the sub-path for the server it wouldn't be an issue but there is currently no option to do so. So what happens is the rest-server sees the incoming user as "/base-url/user" rather than simply "user". I had the server running smoothly on my development machine with the location defined as:

location /sub-path/ {
    proxy_pass http://127.0.0.1:12345/;
}

I'm assuming the nginx.conf that is auto-generated doesn't include the trailing slash? And thus no matching as described with Nginx docs (https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/)

sean

njenkins we have an admin flag that we can activate on our end to change the trailing slash behavior. If you'd like us to activate that for you, then please email our support team to let us know which app and we'll take care of that.

holdenweb

Wow, I'm VERY relieved to know there's an option to re-map subdirectory services from root. The ability to map the same application into multiple sites was one of the things I liked WF for. I presume you had your reasons for defaulting to passing the full path, but I can't imagine what they were. Given that the Opalstack raison d'etre was to serve the WFG community I'm more than mildly surprised, having just spent a head-scratching day figuring out why my remappings weren't working. My thanks to @njenkins!