-
Notifications
You must be signed in to change notification settings - Fork 106
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
Bad Request causes bad JSON response #112
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When querying an invalid column name the JSON response is missing the last curly brace only when the store is instantiated for the session. If session store is not used this issue does not present. This occurs only with bad requests (400).
with store:
{ "message": "Bad Request"
without store:
{ "message": "Bad Request" }
Similar issue here. The workaround posited does fix the problem, but I'm unsure why implementing the store causes the workaround to be necessary.
Express/Session are most recent version as of this post.
Code:
The text was updated successfully, but these errors were encountered: