Allow configuration of upstream proxy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
Been using Toxiproxy for a few months and it is helping out with a lot of my use cases.
It does have a limitation for me at the moment however. I am in a corporate network where all traffic must go through a proxy server before leaving the network. There doesn't seem to be any way to configure ToxiProxy to use this proxy, so I am unable to use toxics when accessing external resources. For us, this is the most useful case, as we can simulate conditions in our internal network already.
Can the functionality be added to allow the following chain:
client -> toxiproxy -> corporate proxy -> external service.
Currently my workaround is to use Fiddler, which will allow the configuration of an upstream proxy, and writing custom scripts to do basically what Toxiproxy does. It would be a lot better if I could just use Toxiproxy.
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
The issue does not identify files, tests, or entry points. Begin by tracing how Toxiproxy currently connects clients to external services, then determine how an upstream corporate proxy would fit into the requested client → Toxiproxy → proxy → external service chain; done means the chain is configurable and usable for external-resource testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100