#30594: Add Cache-Control: private to never_cache decorator.
-------------------------------------+-------------------------------------
Reporter: nsasaki128 | Owner:
| nsasaki128
Type: Bug | Status: assigned
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution:
Keywords: cache | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* 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>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.968ffc4253dab9ec24a7bc7a7ce635d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
