o j$@sdZddlZddlmZddlmZmZddlmZm Z m Z m Z m Z m Z ddlmZddlmZGdd d eZGd d d eZGd d d eeZdS)ai Cache middleware. If enabled, each Django-powered page will be cached based on URL. The canonical way to enable cache middleware is to set ``UpdateCacheMiddleware`` as your first piece of middleware, and ``FetchFromCacheMiddleware`` as the last:: MIDDLEWARE = [ 'django.middleware.cache.UpdateCacheMiddleware', ... 'django.middleware.cache.FetchFromCacheMiddleware' ] This is counterintuitive, but correct: ``UpdateCacheMiddleware`` needs to run last during the response phase, which processes middleware bottom-up; ``FetchFromCacheMiddleware`` needs to run last during the request phase, which processes middleware top-down. The single-class ``CacheMiddleware`` can be used for some simple sites. However, if any other piece of middleware needs to affect the cache key, you'll need to use the two-part ``UpdateCacheMiddleware`` and ``FetchFromCacheMiddleware``. This'll most often happen when you're using Django's ``LocaleMiddleware``. More details about how the caching works: * Only GET or HEAD-requests with status code 200 are cached. * The number of seconds each page is stored for is set by the "max-age" section of the response's "Cache-Control" header, falling back to the CACHE_MIDDLEWARE_SECONDS setting if the section was not found. * This middleware expects that a HEAD request is answered with the same response headers exactly like the corresponding GET request. * When a hit occurs, a shallow copy of the original response object is returned from process_request. * Pages will be cached based on the contents of the request headers listed in the response's "Vary" header. * This middleware also sets ETag, Last-Modified, Expires and Cache-Control headers on the response object. * If the request had an Authorization header and the response was not marked "Cache-Control: public", the response will vary on Authorization. N)settings)DEFAULT_CACHE_ALIAScaches) get_cache_key get_max_agehas_vary_headerlearn_cache_keypatch_response_headerspatch_vary_headers)MiddlewareMixin)parse_http_date_safecs<eZdZdZfddZeddZddZdd ZZ S) UpdateCacheMiddlewarea6 Response-phase cache middleware that updates the cache if the response is cacheable. Must be used as part of the two-part update/fetch cache middleware. UpdateCacheMiddleware must be the first piece of middleware in MIDDLEWARE so that it'll get called last during the response phase. cs.t|tj|_d|_tj|_tj|_ dSN) super__init__rCACHE_MIDDLEWARE_SECONDS cache_timeout page_timeoutCACHE_MIDDLEWARE_KEY_PREFIX key_prefixCACHE_MIDDLEWARE_ALIAS cache_aliasself get_response __class__U/var/www/html/django_cbt/venv/lib/python3.10/site-packages/django/middleware/cache.pyrJs  zUpdateCacheMiddleware.__init__cC t|jSrrrrrrrcacheQ zUpdateCacheMiddleware.cachecCst|do|jS)N_cache_update_cache)hasattrr$rrequestresponserrr_should_update_cacheUsz*UpdateCacheMiddleware._should_update_cachecs4||s|S|js|jdvr|S|jrt|dr|S|ddr3tfdddDr3|St|dr:|Sjd urSt |d urMj nd krS|St ||j d rgd vrgt |d r|jdkrt||jjdt|drt|jr|fdd|Sj||S)zSet the cache, if needed.)i0Cookiez Cache-Controlc3s|]}|vVqdSrr).0 directive) cache_controlrr is  z9UpdateCacheMiddleware.process_response..)privatezno-cachezno-store*Nr Authorizationpublic)r3r*r"rendercsj|Sr)r"set)r) cache_keyrtimeoutrrsz8UpdateCacheMiddleware.process_response..)r) streaming status_codecookiesrgetloweranyrrrr headersr rrr"r%callabler6add_post_render_callbackr7r&r)r/r9rr:rprocess_responseXsD    z&UpdateCacheMiddleware.process_response) __name__ __module__ __qualname____doc__rpropertyr"r)rE __classcell__rrrrr @s  r cs4eZdZdZfddZeddZddZZS)FetchFromCacheMiddlewarea! Request-phase cache middleware that fetches a page from the cache. Must be used as part of the two-part update/fetch cache middleware. FetchFromCacheMiddleware must be the last piece of middleware in MIDDLEWARE so that it'll get called last during the request phase. cs t|tj|_tj|_dSr)rrrrrrrrrrrrs  z!FetchFromCacheMiddleware.__init__cCrrr r!rrrr"r#zFetchFromCacheMiddleware.cachecCs|jdvr d|_dSt||jd|jd}|durd|_dS|j|}|dur<|jdkrs/    W: