> @gustavo thank you very much, it was exactly that problem. > > @Alberto, yes I though about that but as Gustavo pointed out in the > changelog, the error middleware should be the last one to show up and > it was catching the 401 before repoze.who did.
I actually think this solution isn't quite right. We can do as alberto suggests and stop trapping 401's in the error handler, and things should go back to working, unless there's another problem I'm not seeing. And we're dropping the sqlalchemy session with the session removal middleare, and now repoze.what is outside of that so if it tries to do anything on the way out, it won't have an active DBSession. So, the current solution is broken. What's the related problem you had Gustavo? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
