Proxy Pass

[Sathish Kumar]

Hi Rozitis,

Thanks for your reply.




On Thu, May 23, 2019, 10:58 PM Reinis Rozitis <r at roze.lv> wrote:

> > Instead of IP address, if we use FQDN with https, do we have to validate
> the SSL certificate on Proxy_Pass?.
>
> By default the certificate validation is turned off (and nginx just uses
> the ssl for traffic encryption).
> If needed you can enable it with proxy_ssl_verify on; (
> http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_ssl_verify
> )
>
>
> > Due to IP address, multiple sites on the server Nginx access log logging
> the same requests.
>
> If you do the logging on the backend server (and there are multiple
> virtualhosts) and proxy_pass is via http://ip, then you need/have to pass
> also the Host header.
>
> Either by passing the Host header from original request:
>
> proxy_set_header Host $host;
>
> or you can specify a custom one:
>
> proxy_set_header Host "some.domain";
>
>
>
> > Is the above Nginx config, correct way of doing it?.
>
> Depends on your setup and what you want to achieve.
>
>
> For example if your location blocks match the request on the backend you
> can omit the URI in the proxy_pass directive:
>
> location /abc {
> proxy_pass https://1.1.1.1;
> }
>
> rr
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20190524/08c9b2f7/attachment-0001.html>