You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 19, 2023. It is now read-only.
We want to use toxy behind a corporate proxy for resilience testing of our client for a REST service provided by another institution. We can only access the service through the proxy server of our institute. I could not find any configuration options to achieve that. Have I overlooked something?
I tried to use global-agent it fails because the http-proxy dependency used by toxy always creates a new instance of the agent for every request and misses the parameters required by global-agent (because it is and likely cannot be aware of it). Before I raise an issue for http-proxy, I wanted to make sure that I am not overlooking a mechanism of toxy to be run behind a corporate proxy.
Just as a remark the issue with http-proxy is that it does not pass the agent option correctly to the http client API of nodejs. It converts null to false which has a different semantic. Therefore, the following two configuration lines for toxy are passed as false to http.request by http-proxy.
We want to use toxy behind a corporate proxy for resilience testing of our client for a REST service provided by another institution. We can only access the service through the proxy server of our institute. I could not find any configuration options to achieve that. Have I overlooked something?
I tried to use global-agent it fails because the http-proxy dependency used by toxy always creates a new instance of the agent for every request and misses the parameters required by global-agent (because it is and likely cannot be aware of it). Before I raise an issue for http-proxy, I wanted to make sure that I am not overlooking a mechanism of toxy to be run behind a corporate proxy.
Just as a remark the issue with http-proxy is that it does not pass the agent option correctly to the http client API of nodejs. It converts
null
tofalse
which has a different semantic. Therefore, the following two configuration lines for toxy are passed asfalse
tohttp.request
by http-proxy.The text was updated successfully, but these errors were encountered: