Jake Pittis

I can see why you'd rather the caller interpret the exit status. ffcd4366dda5bf9945b36211f63019cdd50f1ea1 adds a `BadExitStatus` error. I haven't updated any of the tests yet. Because a non-zero exit status...

I'm starting to see that this is a more complex change than I originally expected. For example, on my system when I attempt to check the existence of a rule...

I've abandoned this so it's not currently being worked on. Might have time to work on it this weekend.

This can be "fixed" with the following setting: ``` let g:manually_start_socket_repl_plugin = 1 ``` I'm wondering whether this should be on by default and instead we should have: ``` let...

My understanding is that you're suggesting we only allow `127.0.0.1` / `localhost` as upstreams by default? The trouble I see with this is that we likely have a bunch of...

I don't believe that's currently possible. Right now you need to start the container and then hit the HTTP API with "create proxy commands". I feel like the idea of...

Ah good catch @zeisss. The `--config` flag which you can find [here.](https://github.com/Shopify/toxiproxy/blob/master/cmd/toxiproxy.go#L21)

Toxiproxy is "dumb" in that all it does is pass stream data from one port host pair to some upstream port host pair. I don't understand how your `corporate proxy`...

The trouble is that Toxiproxy isn't a "web proxy". It only understands TCP. I don't think we plan on adding any HTTP support any time soon.

Hey @worldtiki. Are you attempting to run Toxiproxy as a side car in a production Kubernetes cluster? If so, I would suggest extreme caution. Toxiproxy was not designed for production...