HTTP Cache docs #573
HTTP Cache docs #573
Conversation
|
I completely disagree. This is going to be part of a larger set of documents, aimed at the expert group of users. |
|
But it's about a setting in config.yml and therefore needs to go into the config section. We wont spread stuff all over the docs again. |
And the other 99% that has to do with everything else? …and the Varnish follow up, that doesn't even touch Bolt? |
|
Well, those Settings should still be on a site in the config section. You can link to it then. Let's talk about that when I am home. I think about a solution in the meantime |
| to cache rendered pages on disk for a period of time. | ||
|
|
||
| This can provide a performance boost on some pages, as means less work for the | ||
| werb server to do in order to serve the requested page repeatedly in a short |
|
|
||
| <p class="note"><strong>Note:</strong> Requests for logged on users will not | ||
| be cached. | ||
| </p> |
There was a problem hiding this comment.
Is this "logged on" users, or any user that has a session? Eg. from Members?
Does it also automatically exclude POST requests for forms?
| -------- | ||
|
|
||
| To enable [Symfony HTTP Cache][] for your Bolt install, in your `config.yml` | ||
| file, find the `caching:` key, and enableing the `request` parameter. |
| ``` | ||
|
|
||
|
|
||
| Fine Tuning Options |
There was a problem hiding this comment.
I think this should be Fine-tuning, right?
Related to bolt/bolt#6023