Decide what error to return to clients who hit an unsupported endpoint
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
Currently if a client hits /upload or /collect on a helper, we return a problem document with unrecognizedTask and HTTP 400 Bad Request. I think either HTTP 404 or HTTP 403, with no response body at all, would be better.
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
Start by tracing the helper request handling for the /upload and /collect endpoints and locating where unrecognizedTask with HTTP 400 is produced. Compare the intended 404 and 403 behavior, including whether either should return a body. Done requires a decided status and response contract, with coverage for unsupported endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100