From d2a0781b03eec21dddbd228e857897955283a81b Mon Sep 17 00:00:00 2001 From: Steve Klabnik Date: Fri, 9 Nov 2012 15:19:40 +0100 Subject: Further explain the CDN and caching situation. --- guides/source/asset_pipeline.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/guides/source/asset_pipeline.md b/guides/source/asset_pipeline.md index 0c5e65ae67..a79a6f10ae 100644 --- a/guides/source/asset_pipeline.md +++ b/guides/source/asset_pipeline.md @@ -582,9 +582,10 @@ your cache forever. This can cause problems. If you use `config.action_controller.perform_caching = true`, Rack::Cache will use `Rails.cache` to store assets. This can cause your cache to fill up quickly. -Every CDN is different, so evaluate how your CDN handles caching and make sure -that it plays nicely with the pipeline; you may find quirks related to your -specific set up. +Every cache is different, so evaluate how your CDN handles caching and make +sure that it plays nicely with the pipeline. You may find quirks related to +your specific set up, you may not. The defaults nginx uses, for example, +should give you no problems when used as an HTTP cache. Customizing the Pipeline ------------------------ -- cgit v1.2.3