Jan Claeys wrote: > Op zo, 23-04-2006 te 18:37 +0200, schreef gabor: >> so when one clicks on the logout link, it's simply not submitted. > [...] >> i don't know what's the correct behavior from the http point of view >> (if a page does not specify any cache-setting, should it be cached or >> not), > > A simple link, a HTTP GET request, shouldn't change any server-side > state or data; that's what HTTP POST is for... > >
you're absolutely right about get/post, but i don't think it would help in this case. for example, take the basic url of a "stock" django application: http://localhost:8000/admin on this url, based on whether the user is authenticated or not, either the login-form,or the list-of-models page should be shown. so if opera caches that page, it might show the wrong page, regardless of what logout-method was used. gabor --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
