This repository has been archived by the owner on Aug 30, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2k
Sending error stack on 500 server error #159
Comments
fixed in the new version |
This was referenced Mar 23, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Isn't it a bad practice security wise to send the error stack trace back to the client in case of uncaught exception?
This is currently what we have on express.js config file:
The text was updated successfully, but these errors were encountered: