Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

minor edits in caching guide

  • Loading branch information...
commit 853439c2bda037884c1214dde3cc8b0da449ed62 1 parent 1db5f4e
@vijaydev vijaydev authored
Showing with 3 additions and 3 deletions.
  1. +3 −3 railties/guides/source/caching_with_rails.textile
View
6 railties/guides/source/caching_with_rails.textile
@@ -64,7 +64,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.
-By default, page caching automatically gzips file (for example, to +products.html.gz+ if user requests +/products+) to reduce size of transmitted data (web servers are typically configured to use a moderate compression ratio as a compromise, but since precompilation happens once, compression ration is maximum).
+By default, page caching automatically gzips files (for example, to +products.html.gz+ if user requests +/products+) to reduce the size of data transmitted (web servers are typically configured to use a moderate compression ratio as a compromise, but since precompilation happens once, compression ratio is maximum).
Nginx is able to serve compressed content directly from disk by enabling +gzip_static+:
@@ -77,13 +77,13 @@ location / {
You can disable gzipping by setting +:gzip+ option to false (for example, if action returns image):
<ruby>
- caches_page :image, :gzip => false
+caches_page :image, :gzip => false
</ruby>
Or, you can set custom gzip compression level (level names are taken from +Zlib+ constants):
<ruby>
- caches_page :image, :gzip => :best_speed
+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+.
Please sign in to comment.
Something went wrong with that request. Please try again.