On Sun, Jul 19, 2009 at 9:08 AM, Ronghui Yu <[email protected]> wrote:
> It proves that it is introduced by > django.middleware.http.ConditionalGetMiddleware. > It returns 304 when requesting the same login page, so at last the browser > uses the former one. > It works fine after removing this middleware. > I believe this middleware cannot work with never_cache. > I think you found a bug in the ConditionalGetMiddleware or the log in page. The content on the page changes due to the token being updated on every reload, so something is wrong there. I would file a ticket in the tracker and post it here. As I said, I have experienced this, and my users find it annoying, so I would like to spend a little more time on it and will try to create a patch when I get a few seconds. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
