User story #5805
open
Improve error display for 500 errors
Description
Currently a few 500 errors, especially via the API don't give any output since it only goes to the specific jetty logfile. Or sometimes, nowhere.
Long-term improvement could be to have a 500 handler page that could read the info from jetty or, less risky, just give the info that a backend error occurred and where to find the actual error message.
Well, and if not that, then at least make sure something gets shown instead of an empty page.
If I can reproduce one I'll update with an API call that triggers it nicely.
Updated by François ARMAND over 9 years ago
Thanks for reporting.
Even it is not apparent with such result, we are trying to give meaningful leads to user when something goes wrong. There is nothing more infuriating than not knowing what goes wrong - especially if the application actually DOES know what went wrong, and just refuse to give that info (at least when no security pb are involved).
So yes, please, help us be better on that !
Updated by Benoît PECCATTE about 9 years ago
- Project changed from 24 to Rudder
- Category set to Techniques