Skip to content
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.

Sign up for GitHub

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

Jump to bottom

use HTTP status code 422 instead of 400 for "correct format but bad values" #418

Open
fiendish opened this issue Aug 22, 2018 · 0 comments
Open

use HTTP status code 422 instead of 400 for "correct format but bad values" #418

fiendish opened this issue Aug 22, 2018 · 0 comments
Labels
feature New functionality

Comments

@fiendish
Copy link
Contributor

fiendish commented Aug 22, 2018 •
edited
Loading

See https://httpstatuses.com/422

422 better fits the situation for e.g. "biospecimen \"BS_HH7SGN2W\" does not exist" responses when trying to post biospecimen-genomic-files entities or similar situations.
@dankolbman dankolbman added the feature New functionality label Nov 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fiendish @dankolbman