发布于 2015-08-27 16:46:19 | 212 次阅读 | 评论: 0 | 来源: 网络整理
小技巧
If you’re using the Symfony Framework, start by reading How to Configure Symfony to Work behind a Load Balancer or a Reverse Proxy.
If you find yourself behind some sort of proxy - like a load balancer - then certain header information may be sent to you using special X-Forwarded-* headers. For example, the Host HTTP header is usually used to return the requested host. But when you’re behind a proxy, the true host may be stored in a X-Forwarded-Host header.
Since HTTP headers can be spoofed, Symfony does not trust these proxy headers by default. If you are behind a proxy, you should manually whitelist your proxy.
2.3 新版功能: CIDR notation support was introduced in Symfony 2.3, so you can whitelist whole subnets (e.g. 10.0.0.0/8, fc00::/7).
use SymfonyComponentHttpFoundationRequest;
// only trust proxy headers coming from this IP addresses
Request::setTrustedProxies(array('192.0.0.1', '10.0.0.0/8'));
By default, the following proxy headers are trusted:
X-Forwarded-For Used in getClientIp();X-Forwarded-Host Used in getHost();X-Forwarded-Port Used in getPort();X-Forwarded-Proto Used in getScheme() and isSecure();If your reverse proxy uses a different header name for any of these, you can configure that header name via setTrustedHeaderName():
Request::setTrustedHeaderName(Request::HEADER_CLIENT_IP, 'X-Proxy-For'); Request::setTrustedHeaderName(Request::HEADER_CLIENT_HOST, 'X-Proxy-Host'); Request::setTrustedHeaderName(Request::HEADER_CLIENT_PORT, 'X-Proxy-Port'); Request::setTrustedHeaderName(Request::HEADER_CLIENT_PROTO, 'X-Proxy-Proto');
By default, if you whitelist your proxy’s IP address, then all four headers listed above are trusted. If you need to trust some of these headers but not others, you can do that as well:
// disables trusting the ``X-Forwarded-Proto`` header, the default header is used Request::setTrustedHeaderName(Request::HEADER_CLIENT_PROTO, '');