From c55bc2e0b2cef20b12099659efb0fb4cf3245a1d Mon Sep 17 00:00:00 2001 From: Ryan Weaver Date: Thu, 7 Aug 2014 11:16:57 -0400 Subject: [PATCH] Adding another note about how AppCache is a reverse proxy at the IP address 127.0.0.1 --- cookbook/request/load_balancer_reverse_proxy.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/cookbook/request/load_balancer_reverse_proxy.rst b/cookbook/request/load_balancer_reverse_proxy.rst index 4dee539a481..a75d68e7abc 100644 --- a/cookbook/request/load_balancer_reverse_proxy.rst +++ b/cookbook/request/load_balancer_reverse_proxy.rst @@ -11,6 +11,12 @@ special ``X-Forwarded-*`` headers. For example, instead of reading the ``REMOTE_ header (which will now be the IP address of your reverse proxy), the user's true IP will be stored in a ``X-Forwarded-For`` header. +.. tip:: + + If your using Symfonys :ref:`AppCache` for caching, + then you *are* using a reverse proxy with the IP address ``127.0.0.1``. + You'll need to configure that address as a trusted proxy below. + If you don't configure Symfony to look for these headers, you'll get incorrect information about the client's IP address, whether or not the client is connecting via HTTPS, the client's port and the hostname being requested.