corrects typo in previous commit
This commit is contained in:
parent
acde75c84a
commit
243cfceba5
|
@ -67,7 +67,7 @@ If you want a more complicated expiration scheme, you can use cache sweepers to
|
|||
|
||||
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. Tipically, a redirection in some before filter that checks request preconditions does the job.
|
||||
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.
|
||||
|
||||
h4. Action Caching
|
||||
|
||||
|
@ -100,7 +100,7 @@ You can modify the default action cache path by passing a +:cache_path+ option.
|
|||
|
||||
Finally, if you are using memcached, you can also pass +:expires_in+. In fact, all parameters not used by +caches_action+ are sent to the underlying cache store.
|
||||
|
||||
INFO: Action caching runs in an after filter. Thus, invalid requests won't generate spurious cache entries as long as you halt them. Tipically, a redirection in some before filter that checks request preconditions does the job.
|
||||
INFO: Action 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.
|
||||
|
||||
h4. Fragment Caching
|
||||
|
||||
|
|
Loading…
Reference in New Issue