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.

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

Describe approach to error handling and fix NotAuthorized HTTP status code #177

Merged
merged 2 commits into from
Apr 2, 2019

Conversation

kevinbader
Copy link
Contributor

Lays out the path for #131 but more work needs to be done in a later PR.

@kevinbader kevinbader added this to the TruBudget 1.0.0-beta.7 milestone Apr 1, 2019
@kevinbader kevinbader force-pushed the 131-error-handling branch 3 times, most recently from c6adeef to 9399e25 Compare April 1, 2019 15:08
Copy link
Contributor

@Stezido Stezido left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice approach. Let's use following Error-Codes:

  • 400 Bad Request: The request cannot be fulfilled due to bad syntax.
  • 401 Unauthorized: Error code response for missing or invalid authentication token.
  • 403 Forbidden: Error code for user not authorized to perform the operation or the resource is unavailable for some reason, but authentication token is OK.
  • 409 Conflict: Whenever a resource conflict would be caused by fulfilling the request. Duplicate entries is an example cause.

@Stezido Stezido merged commit dc50720 into master Apr 2, 2019
@kevinbader kevinbader deleted the 131-error-handling branch April 2, 2019 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants