dmitryfillo / nginx-proxy-pitfalls Goto Github PK

When a variable is used in proxy_pass directive, the location header is not longer adjusted. This causes the value coming from backend to make its way back to client. To get around this, simply set proxy_redirect.

This will not fix up location redirect:

location = /proxy/ {
    set $endpoint proxy.com;
    resolver 8.8.8.8 valid=10s;
    proxy_pass https://$endpoint/;
}

This will:

location = /proxy/ {
    set $endpoint proxy.com;
    resolver 8.8.8.8 valid=10s;
    proxy_pass https://$endpoint/;
    proxy_redirect https://$endpoint/ /;
}

You can define proxy_redirect on server context if used in multiple locations.
This a single line in docs that mention it:

The default parameter is not permitted if proxy_pass is specified using variables.

Based on my own research, unfortunately it does not seem to be possible to force dns lookup for upstream

https://nginx.org/en/docs/http/ngx_http_upstream_module.html

Dynamically configurable group with periodic health checks is available as part of our commercial subscription:

Which allows

upstream dynamic {
    zone upstream_dynamic 64k;

    server backend1.example.com      weight=5;
    server backend2.example.com:8080 fail_timeout=5s slow_start=30s;
    server 192.0.2.1                 max_fails=3;
    server backend3.example.com      **resolve**;
    server backend4.example.com      service=http resolve;

    server backup1.example.com:8080  backup;
    server backup2.example.com:8080  backup;
}

Additionally, the following parameters are available as part of our commercial subscription:

resolve
monitors changes of the IP addresses that correspond to a domain name of the server, and automatically modifies the upstream configuration without the need of restarting nginx (1.5.12). The server group must reside in the shared memory.