Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit574afd5

Browse files
committed
[#6526] some minor tweaks
1 parent691ead1 commit574afd5

File tree

2 files changed

+9
-8
lines changed

2 files changed

+9
-8
lines changed

‎components/http_foundation/trusting_proxies.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ If you find yourself behind some sort of proxy - like a load balancer - then
1313
certain header information may be sent to you using special ``X-Forwarded-*``
1414
headers or the ``Forwarded`` header. For example, the ``Host`` HTTP header is
1515
usually used to return the requested host. But when you're behind a proxy,
16-
the actual host may be stored ina ``X-Forwarded-Host`` header.
16+
the actual host may be stored inan ``X-Forwarded-Host`` header.
1717

1818
Since HTTP headers can be spoofed, Symfony does *not* trust these proxy
1919
headers by default. If you are behind a proxy, you should manually whitelist

‎cookbook/request/load_balancer_reverse_proxy.rst‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,8 @@ the CIDR notation ``10.0.0.0/8``. For more details, see the
6363
:ref:`framework.trusted_proxies<reference-framework-trusted-proxies>` option.
6464

6565
You are also saying that you trust that the proxy does not send conflicting
66-
headers, e.g. sending both X-Forwarded-For and Forwarded in the same request.
66+
headers, e.g. sending both ``X-Forwarded-For`` and ``Forwarded`` in the same
67+
request.
6768

6869
That's it! Symfony will now look for the correct headers to get information
6970
like the client's IP address, host, port and whether the request is
@@ -100,13 +101,13 @@ other information.
100101

101102
.. _cookbook-request-untrust-header:
102103

103-
My Reverse Proxy Sends X-Forwarded-For butdoes not Filter the Forwarded Header
104+
My Reverse Proxy Sends X-Forwarded-For butDoes not Filter the Forwarded Header
104105
-------------------------------------------------------------------------------
105106

106-
Many popular proxy implementations do not yet support the Forwarded header and
107-
do not filter it by default. Ideally, you would configure this
108-
in yourproxy. If this is not possible, you can tell Symfony to distrust
109-
the Forwardedheader, while still trusting your proxy's X-Forwarded-For header.
107+
Many popular proxy implementations do not yet support the``Forwarded`` header
108+
anddo not filter it by default. Ideally, you would configure this in your
109+
proxy. If this is not possible, you can tell Symfony to distrust the ``Forwarded``
110+
header, while still trusting your proxy's``X-Forwarded-For`` header.
110111

111112
This is done inside of your front controller::
112113

@@ -119,7 +120,7 @@ This is done inside of your front controller::
119120
// ...
120121

121122
Configuring the proxy server trust is very important, as not doing so will
122-
malicious users to "spoof" their IP address.
123+
allowmalicious users to "spoof" their IP address.
123124

124125
My Reverse Proxy Uses Non-Standard (not X-Forwarded) Headers
125126
------------------------------------------------------------

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp