From 01dd602150342e0c74ea4af47060e9bd92037e29 Mon Sep 17 00:00:00 2001 From: Gary Wilson Jr Date: Fri, 15 Aug 2008 14:17:24 +0000 Subject: [PATCH] Fixed a ReST error in cache docs. git-svn-id: http://code.djangoproject.com/svn/django/trunk@8378 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/cache.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/cache.txt b/docs/cache.txt index 8f3134e3bc..1a7e63d720 100644 --- a/docs/cache.txt +++ b/docs/cache.txt @@ -231,13 +231,14 @@ arguments. The per-site cache ================== -**New in Django development version** (previous versions of Django only provided -a single ``CacheMiddleware`` instead of the two pieces described below). +**New in Django development version** (previous versions of Django only +provided a single ``CacheMiddleware`` instead of the two pieces described +below). Once the cache is set up, the simplest way to use caching is to cache your entire site. You'll need to add ``'django.middleware.cache.UpdateCacheMiddleware'`` and -``'django.middleware.cache.FetchFromCacheMiddleware' to your +``'django.middleware.cache.FetchFromCacheMiddleware'`` to your ``MIDDLEWARE_CLASSES`` setting, as in this example:: MIDDLEWARE_CLASSES = ( @@ -653,7 +654,7 @@ header. The following middleware modules do so: * ``SessionMiddleware`` adds ``Cookie`` * ``GZipMiddleware`` adds ``Accept-Encoding`` * ``LocaleMiddleware`` adds ``Accept-Language`` - + ``FetchFromCacheMiddleware``, on the other hand, runs during the request phase, where middleware is applied first-to-last, so an item at the top of the list runs *first* during the request phase. The ``FetchFromCacheMiddleware`` also