Apache – Configuring Reverse Proxy Routes with Similar URLs

apache-2.4reverse-proxy

I have this simple reverse proxy setup in my docker container(apache) each mapped to a different microservice with two different docker containers.

#serviceOne 
ProxyPass /abc/xyz/ http://serviceOne:8080/abc/xyz/ Keepalive=On
ProxyPassReverse /abc/xyz/ http://serviceOne:8080/abc/xyz/


#servicetwo 
ProxyPass /abc/xyz/pqr/ http://servicetwo:8080/abc/xyz/pqr/ Keepalive=On
ProxyPassReverse /abc/xyz/pqr/ http://servicetwo:8080/abc/xyz/pqr/

With this in place, I am not able to reach any relative route in the second service such as /abc/xyz/pqr/testprocess is not reachable, while it works properly when only single reverse proxy route is kept.

Best Answer

This was quite obvious and I actually could get it while framing this question :)

in such cases, what matters is the order in which these mappings are placed.

#servicetwo 
ProxyPass /abc/xyz/pqr/ http://servicetwo:8080/abc/xyz/pqr/ Keepalive=On
ProxyPassReverse /abc/xyz/pqr/ http://servicetwo:8080/abc/xyz/pqr/

#serviceOne 
ProxyPass /abc/xyz/ http://serviceOne:8080/abc/xyz/ Keepalive=On
ProxyPassReverse /abc/xyz/ http://serviceOne:8080/abc/xyz/

Just changing the order of these two mappings resolved the issue.

Although this was quite obvious, I could not find anything about reverse proxy URL order in apache documentation.

Even google could not return any solution or might be I could not frame the question properly.

If others could add more technical explanation to this answer, It will be great.

EDIT: There is a clear note about this in the documentation at https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#:~:text=ordering%20or%20override.-,Ordering%20ProxyPass%20Directives,URL.%20Note%20that%20there%20is%20some%20relation%20with%20worker%20sharing,-.

Related Solutions

NGINX Reverse Proxy – URL Rewrite

Any redirect to localhost doesn't make sense from a remote system (e.g. client's Web browser). So the rewrite flags permanent (301) or redirect (302) are not usable in your case.

Please try following setup using a transparent rewrite rule:

location  /foo {
  rewrite /foo/(.*) /$1  break;
  proxy_pass         http://localhost:3200;
  proxy_redirect     off;
  proxy_set_header   Host $host;
}

Use curl -i to test your rewrites. A very subtle change to the rule can cause nginx to perform a redirect.

Nginx Reverse Proxy – How to Setup

I'm not sure this is the correct syntax. Try something like that:

upstream myupstream {
    server 127.0.0.1:8080 fail_timeout=2s;
    keepalive 32;
}

location / {
     proxy_pass http://myupstream;
     proxy_redirect http://myupstream/ /;
}

something along these lines..

But if you just want to redirect port 8080 to 80 why not use a network utility like socat?

Then you should add virtualhosts in nginx for each upstream, and add those virtualhosts in DNS or /etc/hosts, which will all resolve to localhost.

Or you can just avoid the upstream and use virtualhosts like so:

server {
  listen 80;
  server_name myvirtualhost1.local;
  location / {
    proxy_pass http://127.0.0.1:8080;
}

server {
  listen 80;
  server_name myvirtualhost2.local;
  location / {
    proxy_pass http://127.0.0.1:9090;
}

Best Answer

Related Solutions

NGINX Reverse Proxy – URL Rewrite

Nginx Reverse Proxy – How to Setup

Related Topic