diff options
| author | Xavier Noria <fxn@hashref.com> | 2011-03-23 21:52:33 +0100 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2011-03-23 21:52:33 +0100 |
| commit | 3b91b3726dbd7ef6e1f4927d65e2cbe8da12f7c7 (patch) | |
| tree | d0b29e5edb35d20eade90c31442fb7abdfe8872a /railties/guides/source/caching_with_rails.textile | |
| parent | 3a7c7dc73d6111e7c821a81d9c56024dd35769a5 (diff) | |
| parent | ee8ca49414271026575dab70947b446ac6e4b51a (diff) | |
| download | rails-3b91b3726dbd7ef6e1f4927d65e2cbe8da12f7c7.tar.gz rails-3b91b3726dbd7ef6e1f4927d65e2cbe8da12f7c7.tar.bz2 rails-3b91b3726dbd7ef6e1f4927d65e2cbe8da12f7c7.zip | |
Merge branch 'master' of git://github.com/lifo/docrails
Diffstat (limited to 'railties/guides/source/caching_with_rails.textile')
| -rw-r--r-- | railties/guides/source/caching_with_rails.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/caching_with_rails.textile b/railties/guides/source/caching_with_rails.textile index 1b5ec40d16..297ba2d661 100644 --- a/railties/guides/source/caching_with_rails.textile +++ b/railties/guides/source/caching_with_rails.textile @@ -65,7 +65,7 @@ end If you want a more complicated expiration scheme, you can use cache sweepers to expire cached objects when things change. This is covered in the section on Sweepers. -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. Be careful when page caching GET parameters in the URL! +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. Be careful when page caching GET parameters in the URL! 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. |