Handling an Nginx 302 redirect internally, the redirect should go through proxy pass

Question

I have an Nginx configuration that serves an AWS Kibana endpoint.

server {
    listen 0.0.0.0:80;
    location / {
    proxy_pass http://<vpc-elasticsearch-endpoint>/_plugin/kibana/;
    }
}

The problem is: when I access the Nginx URL, I'm redirected to another endpoint with a 302, (AWS cognito) which I can't access from browser.

The cognito URL looks like this : http://vpc-*****.amazonaws.com

I need to resolve the Cognito URL through Nginx itself. Maybe add another location block to resolve Cognito. So that the end user sees the original nginx endpoint that she used to access Nginx before redirected to Cognito.

How to achieve this in Nginx?

score 0 · Answer 1 · answered Jun 25 '19 at 08:59

Try to add Host header to proxy. By default nginx sets it to hostname found in proxy_pass directive.

server {
    listen 0.0.0.0:80;
    location / {
        proxy_pass http://<vpc-elasticsearch-endpoint>/_plugin/kibana/;
        proxy_set_header Host $host;
    }
}

Handling an Nginx 302 redirect internally, the redirect should go through proxy pass

1 Answers1