oxidecomputer / oxidecomputer/dropshot
want server name in headers and errors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 104
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 22
Description
When debugging errors in systems with multiple dropshot servers, it's great to have the request id, but you often want an identifier for the server, too. Some systems have used the x-server-name header for this. How can we support this? Maybe callers can provide an optional server name to use? If we only cared about the headers, then consumers could probably use #1060, but I think we want this in error response bodies, too.
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 reviewing issue #1060 and the existing server and error-response paths. Determine where a caller-provided server name could reach both response headers and error bodies; done means the identifier is consistently exposed in both places without requiring it from callers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100