#33338: Formalize @never_cache setting of Expires header
--------------------------------------+------------------------------------
Reporter: Andy Chosak | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Cache system) | Version: 3.2
Severity: Normal | Resolution:
Keywords: cache | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak):
* type: Uncategorized => Cleanup/optimization
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Agreed, we should clarify that the `Expires` header is added if it isn't
already set in `add_never_cache_headers()` and `@never_cache` docs (see
related `patch_response_headers()`
[https://docs.djangoproject.com/en/stable/ref/utils/#django.utils.cache.patch_response_headerst
docs]). Extra tests are also welcome (as always).
--
Ticket URL: <https://code.djangoproject.com/ticket/33338#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.fa489098e4fce1265ae38ec75cd79987%40djangoproject.com.
