#717: If-Modified-Since checked for exact match
----------------------------------------------------------+-----------------
Reporter: Maniac <[email protected]> | Owner:
adrian
Status: reopened | Milestone:
Component: HTTP handling | Version:
Resolution: | Keywords:
http middleware conditional get if-modified-since
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 1
Needs_better_patch: 0 |
----------------------------------------------------------+-----------------
Changes (by julianb):
* status: closed => reopened
* component: django.contrib.admin => HTTP handling
* needs_tests: 0 => 1
* keywords: => http middleware conditional get if-modified-since
* has_patch: 0 => 1
* resolution: wontfix =>
Comment:
After 5 years, I propose we tackle this. Currently it's not in line with
the RFC (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html).
I have observed Google to often check with a newer Last-Modified date, and
Django replying with "Oh, sure it got modified, but long time before what
you ask, here's the resource anyways: 200 OK"
--
Ticket URL: <http://code.djangoproject.com/ticket/717#comment:7>
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.
