So I'm setting up a virtual path when pointing at a node.js app in my nginx conf. the relevant section looks like so:
location /app {
rewrite /app/(.*) /$1 break;
proxy_pass http://localhost:3000;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
Works great, except that when my node.js app (an express app) calls a redirect.
As an example, the dev box is running nginx on port 8080, and so the url's to the root of the node app looks like:
When I call a redirect to '/app' from node, the actual redirect goes to:
I just had to solve the same problem with Jenkins running behind nginx. What did it for me was to include the server port into the
Host
header that's being sent to Jenkins:Hope that helps.
Per the conversation on this question, the proper resolution is to adjust the proxy's
Host
header directive.Change this:
To this:
$http_host
holds the value as specified in HTTP HOST header, which includes the port. Redirects should pick up the custom port without further customization to OP's setup.These answers (same ticket) elaborate further:
The problem is that the Node.js application is not issuing the redirect correctly. You may be able to use
proxy_redirect
to correct this in nginx:I tried the above solutions, but they all failed whenever the node application issued a fully qualified URL in the location header, such as "http://nodeapp.com:8080/new/location"
So I wound up using the $http_host to pass host and port. And using a match ~^ to rewrite the urls entirely.
In our case, the Node server is running on 8080, and our nginx proxy is running on 8000. This means that every fully qualified URL in a location header needs to be re-written. Hope this helps someone !!