#34048: Do not add cache control header if is set to false or a falsy value
--------------------------------------+------------------------------------
Reporter: Wiktor | Owner: Wiktor
Type: Cleanup/optimization | Status: assigned
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: cache control | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Jan Urban):
This ticket is about avoiding the possible misunderstanding of how `no-
cache` works in browser.
This ticket should not change the functionality of `no-cache` header and
the end result of the `patch_cache_control` and how the header is
interpreted. (As far as I know)
Needs more verification and discussion, if we should lead the hand of
others.
As mentioned as it could be security issue as well if the value is
interpreted wrongly by the others.
I do not know how exactly the `no-cache` works and what are the
conventions for it and best practice, but this sounded like it make it
more explicit.
--
Ticket URL: <https://code.djangoproject.com/ticket/34048#comment:7>
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/010701836fc86bb9-f7a8f042-c321-40ba-bd1c-56579e8e3dc8-000000%40eu-central-1.amazonses.com.
