What browser are you checking with? I've had some problems with IE ignoring the cache-control headers. Do you get the same results in firefox? I just checked the gaeutilities demo, and it's session demo isn't working either, again. I'll take a look at this as soon as I can.
On Nov 17, 4:02 pm, Michael <[EMAIL PROTECTED]> wrote: > Hi, > > I have just tried to setup OpenID login for my app engine application, > following the sample code > fromhttp://code.google.com/p/google-app-engine-samples. > My question is: once successfully logged in, what is the "right way" > of dealing with a logged user throughout multiple requests? > > So far I've done the following: after the consumer.complete() call, I > create a session variable 'claimed_id' and store it using > GAEUtilities' sessions.Session class (http://gaeutilities.appspot.com/ > session). First of all I don't know if this is the intended way of > proceeding, or if it is plainly wrong; secondly, it seems like some > caching on the google servers prevents sessions from working > correctly; for instance, after deleting the session, it takes a few > refreshes before the server response is the right one (even with my > request headers being set to ("Cache-Control": "no-cache,max-age=0" > and "Pragma": "no-cache")). > > Looking forward to hearing from you, > > Michael --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
