theupdateframework / theupdateframework/rust-tuf
tuf/remote: HTTP client with custom/authentication headers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 198
- Forks
- 39
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
I was looking into the feasibility of integrating this crate into a docker client, as the docker registry has a TUF-based trusted distribution extension called notary.
One initial issue I'm seeing is that the docker notary endpoints require authentication via HTTP header, but I'm not seeing any direct way of setting custom headers on the internally-built request. Do you have any suggestions in that direction? Should ConfigBuilder grow some way to take a third-party function which manipulate the RequestBuilder before sending it?
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 ConfigBuilder and the internally built RequestBuilder in the tuf/remote HTTP client. Determine where custom or authentication headers would need to be supplied for Docker Notary endpoints. Done means the project has a decided, usable approach for applying those headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100