-
Notifications
You must be signed in to change notification settings - Fork 77
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
Return better error message when email is not specified #930
Labels
Comments
dev-rahulbhadoriya
pushed a commit
to dev-rahulbhadoriya/central-backend
that referenced
this issue
Dec 14, 2023
2 tasks
dev-rahulbhadoriya
added a commit
to dev-rahulbhadoriya/central-backend
that referenced
this issue
Dec 20, 2023
matthew-white
pushed a commit
that referenced
this issue
Jan 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It looks like /v1/users/reset/initiate will return a 500 error if the request body does not have an
email
property. It'd be better if Central returned a 400 error with a more informative message.We saw such a request in a deployment of Central v2023.3.1. As to why the request body didn't have an
email
property, it looks like theContent-Type
header of the request wasmultipart/form-data
, notapplication/json
. The following error was thrown:The text was updated successfully, but these errors were encountered: