I need to pass some requests to proxy (running GlassFish) with removing one section of url. For example:


Should be passed to proxy as:


I have following Nginx configuration:

upstream vito_api {
    server 178.63.X.X:8080;

server {
    listen 80;
    listen 443 ssl;

    location ~ /jazz/(?<section>.*) {
       proxy_pass http://vito_api/$section/;
       proxy_set_header X-Real-IP $remote_addr;
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

But, unfortunately, request passing without parameters. So, in GlassFish access logs, I can see only:

"148.251.X.X" "NULL-AUTH-USER" "05/Jan/2015:15:18:40 +0100" "GET /MobileApi/ HTTP/1.0" 200 21

What I did wrong? How to pass URL parameters too?

Thank you.

4 Answers 4


From nginx's documentation (context : prefixed location)

If the proxy_pass directive is specified with a URI, then when a request is passed to the server, the part of a normalized request URI matching the location is replaced by a URI specified in the directive.

So it can be simplified with the following :

location /jazz/ {
    proxy_pass http://vito_api/;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  • 1
    This did it for me, however, maybe you can give a clarification to help with this case: https://example.net/jazz/asdf redirects to https://example.net/asdf/ instead of https://example.net/jazz/asdf/. I assume that I may have to tweak the proxied application to not redirect non-trailing-slashed URLs to append a /.
    – Kevin
    Commented Apr 11, 2016 at 19:58
  • 2
    In case anyone else is stumped by this, it's important to note that this only works if your proxy_pass value contains no variables. Commented Aug 24, 2020 at 20:26
  • Thanks @WesCossick I wasted hours trying to understand why it wasn't working, turns out because of variables!!! (which I had to use to another problems).
    – th3n3rd
    Commented Jul 19, 2022 at 12:00

I know this is an old question but I was looking for this and found another and I belive the easiest solution. While using proxy_pass you can't use uri however you can use it as variable. Like here:

location  ~ ^/app/(.*)$ {
# proxy_pass;       # error
proxy_pass$1;      # ok
  • this helped to serve static files behind a backproxy server.
    – Evhz
    Commented Apr 11, 2022 at 16:02

For your question, this will work for you. Use regex.

location ^~ /jazz/ {
    rewrite ^/jazz/(.*)$ /$1? break;
    proxy_pass http://vito_api;
  • if after vito_api; you have UI with static <DNS>/jazz/index.html is convert to <DNS>/index.html and returned 400 errors, how solve? Commented Oct 25, 2022 at 13:12

Andrey, this will not work. Keep it simple :)

According to nginx docs:

In some cases, the part of a request URI to be replaced cannot be determined:

When location is specified using a regular expression. In this case, the directive should be specified without a URI.

So, please,

proxy_pass http://vito_api;
  • 1
    The issue is not the URI in the proxy_pass directive. He misses $is_args$args at the end of the URI and has a trailing slash to be removed. But it can be simplified by using a standard prefixed location, see my answer. Commented Jan 5, 2015 at 20:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .