I have an nginx-based HTTP proxy and I would like to process all HTTP redirects inside it so that clients get only the last response in the redirect chain.

The basic code looks like:

location /proxy {
    rewrite ^/proxy/([^/]+) $1 break;

    proxy_pass http://$uri/;

My attempt at following 1 level redirects is this:

error_page 301 302 307 =200 @redir;

... and having this named location:

location @redir {
    proxy_pass $proxy_location;

Only there's no $proxy_location variable and I failed to find a way of creating it. It should contain the value of Location: header received from upstream.

Any thoughts?


I believe you want the variable $upstream_http_location.

Variables that begin with $proxy* control what goes from nginx to the upstream. The $upstream* series of variables contains information about the response that nginx itself receives. You can get any aribitrary HTTP header received from an upstream server with $upstream_http_headername.

Note that these $upstream variables cannot be anything but null until the response is received from the upstream server, so there are some limitations on their use.

  • 2
    by the rules of stack overflow you should not provide links, which may change in the future. instead you should provide precise working example. I don't know why this incomplete answer was selected but it is not helpful by the stackoveflow standard. vlad's answer is much more helpful.
    – vasilevich
    Oct 23 '20 at 0:41

Here is the full example of what worked for me:

server {

    location / {
        proxy_pass http://backend;
        # You may need to uncomment the following line if your redirects are relative, e.g. /foo/bar
        #proxy_redirect / /;
        proxy_intercept_errors on;
        error_page 301 302 307 = @handle_redirect;

    location @handle_redirect {
        set $saved_redirect_location '$upstream_http_location';
        proxy_pass $saved_redirect_location;
  • 1
    Why did you have to save the value of $upstream_http_location in a new variable?
    – Parth Shah
    Nov 10 '18 at 1:04
  • 1
    I don't know the exact reason, but it doesn't work otherwise... Nov 10 '18 at 7:09
  • This is great but only catches a single redirect. Any way to handle multiple redirects? Oct 18 '19 at 13:17
  • 1
    @ThiefMaster I believe this answer is what you're looking for.
    – iBug
    Oct 24 '19 at 17:11
  • I'm getting the following error 2020/01/23 09:17:46 [error] 1394#0: *1 invalid URL prefix in "", client: xx.xx.28.3, server: www.example.com, request: "GET /test HTTP/1.1", host: "www.example.com" using the @handle_redirect block, any idea ? Jan 23 '20 at 9:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.