Frontend/router should be able to handle authorization failure.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
Currently, store server authoriztion failutre is mapped to ServerErrorCode.Blob_Not_Found. However, router sends request for every replicas for Blob_Not_Found.
Create a new server error code, let router handle it, and finally return http 403 or 401 to client.
Contributor guide
No contributing guide indexed for this repository
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
Trace how store-server authorization failures become ServerErrorCode.Blob_Not_Found, then follow the router path that sends requests to every replica for that code. Identify the error-code handling and HTTP response entry points; done means authorization failures use a distinct code, avoid unnecessary replica requests, and return HTTP 403 or 401 to the client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, authorization, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100