I found a temporary solution, adding the following meta tag to my html head:
<meta http-equiv="Cache-Control" content="no-cache" /> This works, but there should be a more elegant solution. On Oct 5, 4:31 pm, MP <[EMAIL PROTECTED]> wrote: > Symptoms: > > I noticed when I sign out of my app, it takes me to a page which > indicates I am still logged in, which is confusing. When I click > signout in my app, I want it to take me to a page that indicates I am > signed out. This problem occurs with the Google Frontend Server, but > not with the Development Server. > > Diagnosis: > > It looks like the culprit is browser cacheing... my browser caches the > "signed in" version of the page and serves it after I signout. If I > refresh the page again, it returns to the correct state of 'signed > out'. > > My attempt at a solution was to set "Cache-Control" to "no-cache" in > the response headers of all my dynamic pages. This seems to work fine > when I do not have a session cookie stored. However, when the browser > has a session cookie, it seems that the Google Frontend overwrites > "Cache-Control" with "private, max-age=86400". This is what breaks my > signout procedure. > > Question: > > Can I stop the Google Frontend from overriding my Cache-Control header > when the browser has a cookie? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
