Skip to content

Remove redundant references to trusting HttpCache #4239

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

Closed

Conversation

thewilkybarkid
Copy link
Contributor

Q A
Doc fix? yes
New docs? no
Applies to 2.3+
Fixed tickets

Removes references to making HttpCache a trusted proxy as symfony/symfony#11937 would cause it to be handled automatically.

Alternatively it could be reworded, but I'm not sure it's useful to say that this happens (since it was a bit odd to have to configure Symfony to let one part of the code base trust another).

@thewilkybarkid
Copy link
Contributor Author

Whoops, this was meant to be done on 2.3. (IIRC you can fix that can't you?)

@wouterj
Copy link
Member

wouterj commented Sep 16, 2014

(IIRC you can fix that can't you?)

yes :)

@wouterj wouterj changed the title Remove redundant references to trusting HttpCache [WCM] Remove redundant references to trusting HttpCache Sep 16, 2014
@xabbuh xabbuh added the On hold label Sep 17, 2014
fabpot added a commit to symfony/symfony that referenced this pull request Sep 22, 2014
…lkybarkid)

This PR was merged into the 2.3 branch.

Discussion
----------

[HttpKernel] Make sure HttpCache is a trusted proxy

| Q             | A
| ------------- | ---
| Bug fix?      | yes (of sorts)
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #9292
| License       | MIT
| Doc PR        | symfony/symfony-docs#4239

Fixes #9292 by adding `127.0.0.1` as a trusted proxy when using `HttpCache` (assuming it hasn't been already).

Commits
-------

ca65362 Make sure HttpCache is a trusted proxy
fabpot added a commit to symfony/http-kernel that referenced this pull request Sep 22, 2014
…lkybarkid)

This PR was merged into the 2.3 branch.

Discussion
----------

[HttpKernel] Make sure HttpCache is a trusted proxy

| Q             | A
| ------------- | ---
| Bug fix?      | yes (of sorts)
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #9292
| License       | MIT
| Doc PR        | symfony/symfony-docs#4239

Fixes #9292 by adding `127.0.0.1` as a trusted proxy when using `HttpCache` (assuming it hasn't been already).

Commits
-------

ca65362 Make sure HttpCache is a trusted proxy
@xabbuh xabbuh changed the title [WCM] Remove redundant references to trusting HttpCache Remove redundant references to trusting HttpCache Sep 22, 2014
@xabbuh
Copy link
Member

xabbuh commented Sep 22, 2014

Code pull request has been merged.

@weaverryan
Copy link
Member

Great work Chris! Thanks for the updates to the docs and even more for the PR to the core codebase. This makes things easier without any downside I can see. Cheers!

weaverryan added a commit that referenced this pull request Sep 22, 2014
…ilkybarkid)

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

Discussion
----------

Remove redundant references to trusting HttpCache

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | 2.3+
| Fixed tickets |

Removes references to making `HttpCache` a trusted proxy as symfony/symfony#11937 would cause it to be handled automatically.

Alternatively it could be reworded, but I'm not sure it's useful to say that this happens (since it was a bit odd to have to configure Symfony to let one part of the code base trust another).

Commits
-------

8f157dc Remove redundant references to trusting HttpCache
@weaverryan weaverryan closed this Sep 22, 2014
@thewilkybarkid thewilkybarkid deleted the httpcache-trusted-proxy branch September 22, 2014 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants