Uuh, so what's with this? Nothing happened with the ticket and no further comments here either... :(
On Aug 9, 12:28 pm, julianb <[email protected]> wrote: > #717 was posted 5 years ago and closed as wontfix, supposedly cause > Django was in it's early stages and it was not an important issue. I > propose that it's getting reopened and fixed now. > > Like the ticket description says, in ConditionalGetMiddleWare the Last- > Modified date is checked for exact match with If-Modified-Since and > only then a 'Not Modified' response returned. It should however check > if Last-Modified <= If-Modified-Since. This behavior is specified > inhttp://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html(14.25 c) > > Currently a problem is e.g. Google send an If-Modified-Since header > that is not equal to the Last-Modified, often newer in my case. So in > the end, the resource got modified far earlier than Google requests, > Google has the latest version, but Django still sends the full content > instead of 304. > > A patch is already attached and it's working on my production server. -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
