I haven't checked the http headers yet. The tricky thing is that it usually works fine even on the production server! It could be that I set the cookie in a non-standard way, but the session attribute is that a cookie too (I don't know fully how GAE manages sessions)?
On Sunday, August 28, 2011 3:46:10 PM UTC+2, Mike Lawrence wrote: > > have you tried viewing the http headers in each request > using chrome, firebug, httpwatch, etc? > sunshine is the best disinfectant > > I dont think redirects normally can set cookies > maybe the prod server is striping your > invalid host headers on a redirect > > On Aug 28, 7:32 am, Simon Knott <knott...@gmail.com> wrote: > > You're not placing anything in your session which isn't serializable are > > you? > > > > Given that everything seems to be failing when it's starting up a new > > instance, which is when it will attempt to read the session out of the > > datastore/memcache, it may be that it can't deserialize your data. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/Mpn_VNZhhUAJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
