Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.2k
Update http_cache.rst#4809
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
ifdattic commentedJan 11, 2015
Q | A |
---|---|
Doc fix? | yes |
New docs? | no |
Applies to | 2.3 |
Fixed tickets |
| Q | A| ------------- | ---| Doc fix? | yes| New docs? | no| Applies to | 2.3| Fixed tickets |
@@ -856,7 +856,7 @@ If one content corresponds to one URL, the ``PURGE`` model works well. | |||
You send a request to the cache proxy with the HTTP method ``PURGE`` (using | |||
the word "PURGE" is a convention, technically this can be any string) instead | |||
of ``GET`` and make the cache proxy detect this and remove the data from the | |||
cache instead of going toSymfony to get a response. | |||
cache instead of going tothe application to get a response. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
The topic mostly usesapplication and does tie itself to Symfony, as this part is more about general working of cache I think it's a good idea to also just use application
Line 1045, the PHP example doesn't have a great readability and in my opinion could use some improvements |
Please note#4779 , where I've updated the examples. |
Closing in favor of#4861 |