HTTP status codes
Bugs
Description
- I expected the following to happen: If an item is not available in the DB or some error has occurred, I would have expected the DB to throw a proper HTTP status code with some information about what happened.
-
On the contrary, I observed: There's always a
500
thrown with full stack trace (which is a severe security problem).
Program and – if applicable – dependency version
7.8.1