From f7a25eb4808321895bb0908c1d3483bfb5bb1951 Mon Sep 17 00:00:00 2001 From: David Poggi Date: Tue, 28 Feb 2017 13:20:47 -0500 Subject: [PATCH] update ssl.md Make sure we're respecting the respectively ;) --- docs/configuration/ssl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/ssl.md b/docs/configuration/ssl.md index 4c9b25e8f..6d59f6090 100644 --- a/docs/configuration/ssl.md +++ b/docs/configuration/ssl.md @@ -119,7 +119,7 @@ Beware that if you enable the header and a subsequent deploy of your application ## Running behind a load balancer -Your application has access to the HTTP headers `X-Forwarded-Proto`, `X-Forwarded-For` and `X-Forwarded-Port`. These headers indicate the protocol of the original request (HTTP or HTTPS), the port number, and the IP address of the client making the request, respectively. The default configuration is for Nginx to set these headers. +Your application has access to the HTTP headers `X-Forwarded-Proto`, `X-Forwarded-Port` and `X-Forwarded-For`. These headers indicate the protocol of the original request (HTTP or HTTPS), the port number, and the IP address of the client making the request, respectively. The default configuration is for Nginx to set these headers. If your server runs behind an HTTP/S load balancer, then Nginx will see all requests as coming from the load balancer. If your load balancer sets the `X-Forwarded-` headers, you can tell Nginx to pass these headers from load balancer to your application by using the following [nginx custom template](/dokku/configuration/nginx/#customizing-the-nginx-configuration)