Currently Django's never_cache lacks Cache-Control: private, so I suggest
to add this header to a response.
Thanks,
--
Ticket URL: <https://code.djangoproject.com/ticket/30594>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: nsasaki128 (added)
* needs_docs: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/30594#comment:1>
* status: new => assigned
* cc: Florian Apolloner (added)
* component: Utilities => Core (Cache system)
* owner: nobody => nsasaki128
* has_patch: 0 => 1
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
Thanks for the report. Sounds reasonable, due to the
[https://tools.ietf.org/html/rfc2616#section-14.9.1 rfc2616]:
> "private" - Indicates that all or part of the response message is
intended for a single user and MUST NOT be cached by a shared cache.
[https://github.com/django/django/pull/11514 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/30594#comment:2>
* type: Bug => New feature
--
Ticket URL: <https://code.djangoproject.com/ticket/30594#comment:3>
* needs_docs: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/30594#comment:4>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a289e7967907f47e8aba2b25e5f397af6ac7dac9" a289e796]:
{{{
#!CommitTicketReference repository=""
revision="a289e7967907f47e8aba2b25e5f397af6ac7dac9"
Fixed #30594 -- Added 'private' Cache-Control directive to never_cache()
decorator.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30594#comment:5>