Support HEAD request for /hpke_config endpoint.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 16
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 30
Description
Currently, we support only the literal GET HTTP verb against the /hpke_config endpoint.
Other than it being nice to support standard HTTP verbs, supporting HEAD is also useful to allow folks to check caching headers like ETag & Last-Modified. (N.B. we don't currently set these headers)
This concern applies to all endpoints that support the GET verb; it just so happens that /hpke_config is the only endpoint that supports GET right now.
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 locating the routing and handler entry point for the /hpke_config endpoint, then inspect how it currently matches the GET verb. Add coverage for a HEAD request and verify that the endpoint accepts HEAD while preserving the existing GET behavior; caching headers are not currently part of this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100