Actions
User story #5805
openImprove error display for 500 errors
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
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.
Actions