#30594: Add Cache-Control: private to never_cache decorator
-----------------------------------------+------------------------
Reporter: nsasaki128 | Owner: nobody
Type: Uncategorized | Status: new
Component: Utilities | Version: master
Severity: Normal | Keywords: cache
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
If a Django user wants to ensure that a resource is not cached.
The user might use never_cache decorator, however, sometimes it doesn't
work as he or she expected, which means the resource is cached by CDN.
The reason why is that CDN providers cache the resource. For example,
Fastly needs to set Cache-Control: private for HTTP header with the origin
response. The document is below.
https://docs.fastly.com/guides/tutorials/cache-control-tutorial#do-not-
cache
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.
--
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/053.9e68cf61372698b2834e8365ef10c968%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.