diff options
| author | Justin <justin@brightal.com> | 2013-03-15 13:26:08 +0530 |
|---|---|---|
| committer | Carlos Antonio da Silva <carlosantoniodasilva@gmail.com> | 2013-03-15 09:48:27 -0300 |
| commit | 1c2717d3f5a3ce0ea97f832d1d008e053ad47acd (patch) | |
| tree | 609b44de9f6a7919120058017d065ec5587a90a8 | |
| parent | 9d5699a05ca625d531988d563d2eda7e4b290fed (diff) | |
| download | rails-1c2717d3f5a3ce0ea97f832d1d008e053ad47acd.tar.gz rails-1c2717d3f5a3ce0ea97f832d1d008e053ad47acd.tar.bz2 rails-1c2717d3f5a3ce0ea97f832d1d008e053ad47acd.zip | |
Typo fix [ci ski]
Closes #9730.
| -rw-r--r-- | railties/guides/source/caching_with_rails.textile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/railties/guides/source/caching_with_rails.textile b/railties/guides/source/caching_with_rails.textile index 0e811a2527..c2ca5a335d 100644 --- a/railties/guides/source/caching_with_rails.textile +++ b/railties/guides/source/caching_with_rails.textile @@ -86,9 +86,9 @@ Or, you can set custom gzip compression level (level names are taken from +Zlib+ caches_page :image, :gzip => :best_speed </ruby> -NOTE: Page caching ignores all parameters. For example +/products?page=1+ will be written out to the filesystem as +products.html+ with no reference to the +page+ parameter. Thus, if someone requests +/products?page=2+ later, they will get the cached first page. A workaround for this limitation is to include the parameters in the page's path, e.g. +/productions/page/1+. +NOTE: Page caching ignores all parameters. For example +/products?page=1+ will be written out to the filesystem as +products.html+ with no reference to the +page+ parameter. Thus, if someone requests +/products?page=2+ later, they will get the cached first page. A workaround for this limitation is to include the parameters in the products's path, e.g. +/products/page/1+. -INFO: Page caching runs in an after filter. Thus, invalid requests won't generate spurious cache entries as long as you halt them. Typically, a redirection in some before filter that checks request preconditions does the job. +INFO: Page caching runs as an after filter. Thus, invalid requests won't generate spurious cache entries as long as you halt them. Typically, a redirection in some before filter that checks request preconditions does the job. h4. Action Caching |