I have used routes mapping and a WSGI webdav app to implement WebDAV in my TG2 project.
Based on the schematic of request flow through the TG stack[1] I had expected my webdav app to have repoze.who/what middleware, but it appears I have to explicitly add my authentication/authorization middleware explicitly. That's not a big deal, its not a big deal to have it add it myself, but I'm worried I'm misunderstanding how this all works. Where it does matter, is that in my WebDav app, if there are any, say HTTPUnauthorized (401) or HTTPRedirect (302) exceptions raised, these aren't "translated" into the appropriate HTTP response, they are raised as errors by the debugger and the fancy debug page is displayed. Is there another piece of middleware that normally looks after this that I will also have to add manually or is there something more fundamental that I'm misunderstanding? [1] http://www.turbogears.org/2.0/docs/main/RequestFlow.html Thanks Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en -~----------~----~----~----~------~----~------~--~---
