@@ -7,7 +7,7 @@ an AWS Elastic Load Balancer) or a reverse proxy (e.g. Varnish for
7
7
8
8
For the most part, this doesn't cause any problems with Symfony. But, when
9
9
a request passes through a proxy, certain request information is sent using
10
- either the standard ``Forwarded `` header or non standard special ``X-Forwarded-* ``
10
+ either the standard ``Forwarded `` header or non- standard special ``X-Forwarded-* ``
11
11
headers. For example, instead of reading the ``REMOTE_ADDR `` header (which
12
12
will now be the IP address of your reverse proxy), the user's true IP will be
13
13
stored in a standard ``Forwarded: for="..." `` header or a non standard
@@ -95,12 +95,12 @@ other information.
95
95
My Reverse Proxy Uses Non-Standard (not X-Forwarded) Headers
96
96
------------------------------------------------------------
97
97
98
- Although `rfc7239 `_ recently defined a standard ``Forwarded `` header to disclose
99
- all proxy information, most reverse proxies store information on non standard
98
+ Although `RFC 7239 `_ recently defined a standard ``Forwarded `` header to disclose
99
+ all proxy information, most reverse proxies store information on non- standard
100
100
``X-Forwarded-* `` headers.
101
101
But if your reverse proxy uses other non-standard header names, you can configure
102
102
these (see ":doc: `/components/http_foundation/trusting_proxies `").
103
103
The code for doing this will need to live in your front controller (e.g. ``web/app.php ``).
104
104
105
105
.. _`security groups` : http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/using-elb-security-groups.html
106
- .. _`rfc7239 ` : http://tools.ietf.org/html/rfc7239
106
+ .. _`RFC 7239 ` : http://tools.ietf.org/html/rfc7239
0 commit comments