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

Adjust incorrectly employed HTTP codes #359

Open
3 tasks
fmigneault opened this issue Oct 5, 2020 · 0 comments
Open
3 tasks

Adjust incorrectly employed HTTP codes #359

fmigneault opened this issue Oct 5, 2020 · 0 comments
Assignees
@fmigneault
Labels
enhancement Improvements in term of performance or behaviour feature New feature to be developed
Milestone
Backlog

Comments

@fmigneault
Copy link
Collaborator

fmigneault commented Oct 5, 2020 •
edited
Loading

Following issues must be addressed:

  • 400 for semantically incorrect requests (eg: body is not parseable JSON) and 422 for semantically correct but invalid data for the given request (eg: wrong type, missing field, etc.)
  • 500 instead of 403 for database operations, 403 only for literal forbidden access according to user/group-permissions
    (duplicates Should other response than 403 be used for forbidden access due to db problem #331) (eg: forbidden update of anonymous information is correct usage)
  • ...?
@fmigneault fmigneault added enhancement Improvements in term of performance or behaviour feature New feature to be developed labels Oct 5, 2020
@fmigneault fmigneault self-assigned this Oct 5, 2020
fmigneault added a commit that referenced this issue Oct 14, 2020
@fmigneault
ServiceAccess tests + adjust 400->403 for forbidden children resource…
f6e7b8d 
… creation (relates to #359)
@fmigneault fmigneault added this to the Backlog milestone May 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fmigneault fmigneault

Labels
enhancement Improvements in term of performance or behaviour feature New feature to be developed
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
1 participant
@fmigneault