Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix adding implicitly rendered template digests to ETags | Javan Makhmali | 2016-06-28 | 1 | -1/+7 |
| | | | | Signed-off-by: Jeremy Daer <jeremydaer@gmail.com> | ||||
* | Remove unused block arguments | deepj | 2015-08-23 | 1 | -1/+1 |
| | |||||
* | Wrap code snippets in +, not backticks, in sdoc | claudiob | 2014-11-20 | 1 | -2/+2 |
| | | | | | | | | I grepped the source code for code snippets wrapped in backticks in the comments and replaced the backticks with plus signs so they are correctly displayed in the Rails documentation. [ci skip] | ||||
* | When your templates change, browser caches bust automatically. | Jeremy Kemper | 2014-08-17 | 1 | -0/+50 |
New default: the template digest is automatically included in your ETags. When you call `fresh_when @post`, the digest for `posts/show.html.erb` is mixed in so future changes to the HTML will blow HTTP caches for you. This makes it easy to HTTP-cache many more of your actions. If you render a different template, you can now pass the `:template` option to include its digest instead: fresh_when @post, template: 'widgets/show' Pass `template: false` to skip the lookup. To turn this off entirely, set: config.action_controller.etag_with_template_digest = false |