-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prod stacktraces are returned to client for unhandled 500 errors #549
Comments
Related to #448 |
yeah i did do this intentionally.. better to have error information than not and it's an open source project anyway. |
Servers running open source software still have secrets 🙃 Example: brianc/node-postgres#1568 |
sure but a stack trace? things are hard enough to debug w community software .. |
We don't surface the stack trace in Frontend, and in practice over the years, I don't think we've used the |
One example of something you wouldn't want forwarded to a user: brianc/node-postgres#3145 |
E.g.
Possibly written at: https://github.com/getodk/central-backend/blob/master/lib/http/endpoint.js#L202-L211
The text was updated successfully, but these errors were encountered: