Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[load_balancer_reverse_proxy ] Always use 127.0.0.1 as a trusted proxy #5513

Closed
wants to merge 1 commit into from

Conversation

ruudk
Copy link
Contributor

@ruudk ruudk commented Jul 10, 2015

Apparently the behaviour changed in Symfony 2.7. Before, the solution just worked perfectly with a Amazon ELB. After upgrading to Symfony 2.7 the subrequests weren't trusted anymore because they set the REMOTE_ADDR to 127.0.0.1

Apparently the behaviour changed in Symfony 2.7. Before, the solution just worked perfectly with a Amazon ELB. After upgrading to Symfony 2.7 the subrequests weren't trusted anymore because they set the `REMOTE_ADDR` to `127.0.0.1`
@xabbuh
Copy link
Member

xabbuh commented Dec 17, 2015

I guess that is related to the security fix described in http://symfony.com/blog/cve-2015-2309-unsafe-methods-in-the-request-class, isn't it? Then it must be merged into the 2.3 branch.

@wouterj
Copy link
Member

wouterj commented Feb 6, 2016

Thank you Ruud! I'm sorry for the big delay on merging this, but I think it's a valid change. I've merged it into the 2.3 docs, as proposed by @xabbuh.

wouterj added a commit that referenced this pull request Feb 6, 2016
…usted proxy (ruudk)

This PR was submitted for the 2.7 branch but it was merged into the 2.3 branch instead (closes #5513).

Discussion
----------

[load_balancer_reverse_proxy ] Always use 127.0.0.1 as a trusted proxy

Apparently the behaviour changed in Symfony 2.7. Before, the solution just worked perfectly with a Amazon ELB. After upgrading to Symfony 2.7 the subrequests weren't trusted anymore because they set the `REMOTE_ADDR` to `127.0.0.1`

Commits
-------

9b2c9f4 Always use 127.0.0.1 as a trusted proxy
@wouterj wouterj closed this Feb 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants