I think I posted the wrong issue, turns out 588 was a result of a pickling error that did exist at one time in appengine. I actually had to hold off on doing the data structure storage for cache and session until it was fixed. However, point taken on the data coming from a cookie. I'll wrap handling the flash data in a try statement to handle if the data is invalid for 1.0rc3. I should have thought of that sooner.
On Oct 19, 8:55 am, Ross Ridge <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > I've still got the same person who inconsistently runs into the error, > > when connecting to the demo athttp://gaeutilities.appspot.com/session > > > The error can be reproduced by this user, but I can not. However, I've > > verified in my logs that the error is happening for them. This was a > > problem before issue 588 was resolved, which is what leads me to > > believe somehow the server he is connecting to the application through > > is not up to date. > > Issue 588 isn't marked as being resolved. It's also not obvious that > problem you reported there is a result of a bug in the Googe App > Engine software. Except for one function at the bottom of the stack, > your traceback only shows your code and code from the standard Python > module pickle. > > Hmm... if you're unpickling HTTP cookies, you probably want to rethink > that. The documentation for the pickle module warns: > > Warning: The pickle module is not intended to be secure against > erroneous or maliciously constructed data. Never unpickle data > received from an untrusted or unauthenticated source. > > Ross Ridge --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
