{"id":75827,"date":"2020-01-20T12:18:48","date_gmt":"2020-01-20T06:48:48","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=75827"},"modified":"2024-04-12T14:17:19","modified_gmt":"2024-04-12T08:47:19","slug":"the-per-site-cache","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/the-per-site-cache\/","title":{"rendered":"The Per-Site Cache"},"content":{"rendered":"

Once the cache is set up, the simplest way to use caching is to cache your entire site. You\u2019ll need to<\/p>\n

add                                                                     ‘django.middleware.cache.UpdateCacheMiddleware’ and ‘django.middleware.cache.FetchFromCacheMiddleware’ to your MIDDLEWARE_CLASSES setting, as in this example:<\/p>\n

MIDDLEWARE_CLASSES = [
\n‘django.middleware.cache.UpdateCacheMiddleware’,
\n‘django.middleware.common.CommonMiddleware’,
\n‘django.middleware.cache.FetchFromCacheMiddleware’,
\n]\n

No, that\u2019s not a typo: the update middleware must be first in the list, and the fetch middleware must be last. The details are a bit obscure, but see Order of MIDDLEWARE_CLASSES in the next chapter if you\u2019d like the full story.<\/p>\n

Then, add the following required settings to your Django settings file:<\/p>\n