#10225: Cache middleware does not honor "Cache-Control: no-cache" in request
headers
-----------------------------------+----------------------------------------
Reporter: erny | Owner: nobody
Status: new | Milestone:
Component: Cache system | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by julianb):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
I can confirm that. Sending "no-cache" does not give you a fresh page
which means it is not following specification:
"The request includes a "no-cache" cache-control directive or, for
compatibility with HTTP/1.0 clients, "Pragma: no-cache". Field names MUST
NOT be included with the no-cache directive in a request. The server MUST
NOT use a cached copy when responding to such a request."
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
--
Ticket URL: <http://code.djangoproject.com/ticket/10225#comment:1>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
