Support HTTPS for Toxiproxy API server
Open
Nobody has claimed this yet.
ideas
Toxiproxy
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
Currently API could be accessed only via HTTP.
Make HTTPS would simplify some extra work to run extra reverse proxy with HTTPS support.
Possible example of set HTTPS config:
toxiproxy --cert <bundle certificate file> --cert-key <private key> --listen https://0.0.0.0:8083
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 API server startup and command-line handling for the listen address. Add support for the proposed certificate, private-key, and HTTPS listen options, then verify that the API server accepts HTTPS connections using the supplied certificate and key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100