Re: [google-appengine] Re: Security Constraint works in hosted mode but on the App Engine

2011-05-03 Thread Robert Kluin
Hi, The cookie used for login info on the dev server is just a session cookie; the production cookie is not. That is why you're seeing the production logins last a lot longer. Robert On Tue, May 3, 2011 at 13:55, DFB wrote: > Just reflecting back on it, I'm not sure why it always worke

[google-appengine] Re: Security Constraint works in hosted mode but on the App Engine

2011-05-03 Thread DFB
Just reflecting back on it, I'm not sure why it always worked in the hosted mode. Probably it doesn't read the files from the cache in the hosted mode, and that misled me into thinking that something was wrong with GAE. Well anyway ... On May 4, 1:52 am, DFB wrote: > Hi Robert, > > I think the pr

[google-appengine] Re: Security Constraint works in hosted mode but on the App Engine

2011-05-03 Thread DFB
Hi Robert, I think the problem was the cache and my understanding of how browser 'stealth' modes work. I thought if I open up a fresh 'stealth' mode window in a browser such as Chrome, it would not read anything from the cache. But apparently, it doesn't work that way. It still reads the file from

[google-appengine] Re: Security Constraint works in hosted mode but on the App Engine

2011-05-03 Thread DFB
Thanks for your response. I'm surely not logged in. And definitely not logged in with the admin account. I have also tried it from different browsers, different machines, and using the stealth mode. I also tried with the url "/ds/*" but that doesn't work either. Both urls work in the hosted mode