From b2e05910edd1d077bd40f1353883031ddb5a255a Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Sat, 12 Nov 2005 18:17:22 +0000 Subject: [PATCH] Fixed #773 -- Removed reference to CACHE_MIDDLEWARE_GZIP in docs/cache.txt. Thanks, Eugene git-svn-id: http://code.djangoproject.com/svn/django/trunk@1200 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/cache.txt | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/cache.txt b/docs/cache.txt index f8986b9115..c426811219 100644 --- a/docs/cache.txt +++ b/docs/cache.txt @@ -101,12 +101,6 @@ Then, add the following three required settings to your Django settings file: sites using the same Django installation, set this to the name of the site, or some other string that is unique to this Django instance, to prevent key collisions. Use an empty string if you don't care. -* ``CACHE_MIDDLEWARE_GZIP`` -- Either ``True`` or ``False``. If this is - enabled, Django will gzip all content for users whose browsers support gzip - encoding. Using gzip adds a level of overhead to page requests, but the - overhead generally is cancelled out by the fact that gzipped pages are stored - in the cache. That means subsequent requests won't have the overhead of - zipping, and the cache will hold more pages because each one is smaller. The cache middleware caches every page that doesn't have GET or POST parameters. Additionally, ``CacheMiddleware`` automatically sets a few headers