o uvXj)@s~dZddlmZddlmZmZddlmZmZm Z m Z m Z ddl m Z Gddde ZGdd d e ZGd d d eeZd S) a 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 counter-intuitive, 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. )settings)DEFAULT_CACHE_ALIAScaches) get_cache_key get_max_agehas_vary_headerlearn_cache_keypatch_response_headers)MiddlewareMixinc@s*eZdZdZd ddZddZddZdS) 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. NcCs.tj|_tj|_tj|_t|j|_||_ dSN) rCACHE_MIDDLEWARE_SECONDS cache_timeoutCACHE_MIDDLEWARE_KEY_PREFIX key_prefixCACHE_MIDDLEWARE_ALIAS cache_aliasrcache get_responseselfrrT/var/www/html/myproject/venv/lib/python3.10/site-packages/django/middleware/cache.py__init__@s   zUpdateCacheMiddleware.__init__cCst|do|jS)N_cache_update_cache)hasattrrrrequestresponserrr_should_update_cacheGsz*UpdateCacheMiddleware._should_update_cachecs||s|S|js|jdvr|S|js|jrt|dr|Sd|ddvr)|St|dur5jndkr;|St |rq|jdkrqt ||j j d t |d rit|jri|fd d |Sj ||S) zSet the cache, if needed.)i0Cookieprivatez Cache-ControlrNrr rrendercsj|Sr )rset)r cache_keyrtimeoutrrjsz8UpdateCacheMiddleware.process_response..)r streaming status_codeCOOKIEScookiesrgetrrr rrrrcallabler$add_post_render_callbackr%rrr'rprocess_responseJs.  z&UpdateCacheMiddleware.process_responser )__name__ __module__ __qualname____doc__rrr2rrrrr 7s   r c@s"eZdZdZdddZddZdS)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. NcCs&tj|_tj|_t|j|_||_dSr )rrrrrrrrrrrrrys  z!FetchFromCacheMiddleware.__init__cCs|jdvr d|_dSt||jd|jd}|durd|_dS|j|}|dur<|jdkrs - :+