#34048: Do not add cache control header if is set to false or a falsy value
-------------------------------+--------------------------------------
Reporter: Wiktor | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: dev
Severity: Normal | Resolution:
Keywords: cache control | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Description changed by Wiktor:
Old description:
> Currently when one sets no_cache to a falsy value, e.g.:
>
> {{{
> @cache_control(no_cache=False)
> def some_view()
> pass
> }}}
>
> Cache-Control header will be set to no_cache=False.
>
> This might be confusing and might lead to a security issue.
New description:
Currently when one sets no_cache to a falsy value, e.g.:
{{{
@cache_control(no_cache=False)
def some_view()
pass
}}}
Cache-Control header will be set to no_cache=False.
This might be confusing and might lead to a security issue.
Instead it should be just excluded.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/34048#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701836f992e54-0883bb13-ea45-4867-970b-98709d16fb29-000000%40eu-central-1.amazonses.com.
