Report correct status code on streams
Open
Nobody has claimed this yet.
backend
- Dominant language
- C++
- Stars
- 46
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
When accessing streams via `/name` the status code is always 200, even though the stream might not exist. Currently there is no nice fix since stream-existence is only checked client-side via the API.
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 request handling for streams accessed through the /name route and the client-side API check for stream existence. Determine how missing streams are represented and make the route return the appropriate non-200 status while preserving successful responses for existing streams.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100