Description
In moin/1.9 as of 2008-11-27, exception handling is (at least partly) broken.
You often just get some "400 Bad Request" and that's it.
No traceback in the browser, no traceback logged via the logging framework. Now guess what caused the problem...
Steps to reproduce
See my recent fixes in 1.9, they often showed that behaviour before I fixed them.
Component selection
- top level exception handler
Details
MoinMoin Version |
1.9alpha as of 2008-11-27 |
OS and Version |
Linux |
Python Version |
2.4 |
Server Setup |
apache / mod_wsgi |
Server Details |
|
Language you are using the wiki in (set in the browser/UserPreferences) |
|
Workaround
The standalone server (wikiserver.py) seems to behave a bit different by emitting a traceback to the console.
Discussion
Exceptions should always get logged in the same way (on the moin wsgi application level), so it does not matter what server setup you use.
Maybe there should be 2 modes:
- debug mode for development: produce web tracebacks
- production mode: produce some web hint where to find the traceback, but don't show details
- ever log the traceback to the logging framework
Plan
- Priority:
- Assigned to:
Status: should be fixed by: http://hg.moinmo.in/moin/1.9/rev/edb6cb2cac43 (we catch all exceptions in the wsgi application, log them via the logging framework, and re-raise them in case there is another error handler or debugger middleware more far above)