On Sep 5, 2:42 pm, Chris McDonough <[email protected]> wrote: > Sounds like a bug. I've added an issue you can track > here:https://github.com/Pylons/pyramid/issues/262
Wow, and it's already been fixed, too! :-) Thank you, Chris and Michael, for the very quick turn-around. Unfortunately, upgrading to pyramid 1.2 is not an option right now. That said: For anyone else who runs into this, here's my work-around: *don't* call pyramid.security.authenticated_userid in my logout view. According to my reading of pyramid/authentication.py, that call ends up in pyramid.authentication.AuthTktCookieHelper.identify, which is what triggers the new ticket. And the only reason my logout view calls authenticated_userid is to log the id of the user who is logging out. For now, I'll forgo the log entry for a clean log out sequence (or I'll decode the content of the cookie myself at the expense of a handful of good design principles). Thanks, Dan -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
