OpenBankProject / OpenBankProject/OBP-API
400 Bad Request with no message being returned where more return info is expected
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
Exception message issue.
When a request is performed for which an error is returned (example below), some detail is required to inform the user about the status and what the error actually is.
Example:
Should return a more meaningful message than
400 Bad Request
{
"error": "error"
}
Suggested response code detail:
403 Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the request to the listed OBP API endpoint and trace where its generic 400 response is produced. Determine how the underlying error should map to a meaningful status and message, including the suggested permission-related 403 case; done means the response explains the failure instead of returning only {"error":"error"}.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100