Fix typo and tweak markup.

This commit is contained in:
Berker Peksag 2015-05-29 06:46:28 +03:00
parent 3c2533d122
commit 308f10f398

View File

@ -111,20 +111,20 @@ Gunicorn may come from untrusted proxies or directly from clients since the
application may be tricked into serving SSL-only content over an insecure application may be tricked into serving SSL-only content over an insecure
connection. connection.
Gunicorn v19 introduced a breaking change concerning how ``REMOTE_ADDR`` is Gunicorn 19 introduced a breaking change concerning how ``REMOTE_ADDR`` is
handled. Previous to Gunicorn v19 this was set to the value of handled. Previous to Gunicorn 19 this was set to the value of
``X-Forwarded-For`` if recieved from a trusted proxy. However, this was not in ``X-Forwarded-For`` if received from a trusted proxy. However, this was not in
compliance with `RFC 3875 CGI Version 1.1 <http://www.ietf.org/rfc/rfc3875>`_ compliance with :rfc:`3875` which is why the ``REMOTE_ADDR`` is now the IP
which is why the ``REMOTE_ADDR`` is now the IP address of **the proxy** and address of **the proxy** and **not the actual user**. You should instead
**not the actual user**. You should instead configure Nginx to send the user's configure Nginx to send the user's IP address through the ``X-Forwarded-For``
IP address through the ``X-Forwarded-For`` header like this:: header like this::
... ...
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
... ...
It is also worth noting that the ``REMOTE_ADDR`` will be completely empty if you It is also worth noting that the ``REMOTE_ADDR`` will be completely empty if
bind Gunicorn to a unix socket and not a tcp host:port tuple. you bind Gunicorn to a UNIX socket and not a TCP ``host:port`` tuple.
Using Virtualenv Using Virtualenv
================ ================