You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of people have problems when their app is behind a load balancer or a reverse proxy: they don't have the right HTTP port, or isSecure does not return the right value.
We should probably have a dedicated cookbook about this topic and how you can use Request::setTrustedHeaderName(), Request::setTrustedProxies(), the HTTP(S) port configuration in the settings, ...
The text was updated successfully, but these errors were encountered:
First Sorry , Handsome, i clicked the [Report Abuse] for a mistake , beg for pardon, Sorry !!!!!!
555555555
Next Content:
Symfony Version is 2.2, with Chrome,Charact is UTF-8, there is a 500 , 500 Internal Server Error - ServiceException, Why i can not see the Chinese ? instead of wrong code ?
miss some compoents ?
I Want to slove it...
…rk (weaverryan)
This PR was merged into the 2.3 branch.
Discussion
----------
Adding a new entry about reverse proxies in the framework
Hi guys!
| Q | A
| ------------- | ---
| Doc fix? | no
| New docs? | no
| Applies to | all (or 2.3+)
| Fixed tickets | #2946#2491
Per #2491, I wanted to answer the simple question: "What do I need to do in order to configure Symfony if I have a reverse proxy". The `trusted_proxies` is already documented in the reference section, but this is a full walk-through of what you should be doing and why. I've also increased links in several places where notes are needed.
Thanks!
Commits
-------
5ab6c4a Title case fix thanks to @xabbuh!
89e4d9d A bunch of changes thanks to @xabbuh and @stof81053ab Fixing build error
c55bc2e Adding another note about how AppCache is a reverse proxy at the IP address 127.0.0.1
18af4e8 Adding a new entry about reverse proxies in the framework and linking to it in many places
A lot of people have problems when their app is behind a load balancer or a reverse proxy: they don't have the right HTTP port, or isSecure does not return the right value.
We should probably have a dedicated cookbook about this topic and how you can use
Request::setTrustedHeaderName()
,Request::setTrustedProxies()
, the HTTP(S) port configuration in the settings, ...The text was updated successfully, but these errors were encountered: