-
Notifications
You must be signed in to change notification settings - Fork 280
Support for http(s)_proxy #51
Comments
Can you be please more specific? How would you expect this to work? |
If the environment variables http_proxy and/or https_proxy are set, they should be leveraged in the call. I think this StackOverflow answer has a somewhat correct implementation (to be platform agnostic, it'd need to function if those variables are not set). (disclaimer, I'm completely new to node/coffeescript) http://stackoverflow.com/questions/3862813/how-can-i-use-an-http-proxy-with-node-js-http-client |
I also ran into this. How do I tell dredd to use a http proxy? |
The nodejs people think it's not worth implementing in the http/https libraries. It looks like it might be worthwhile to switch from node's http/https libraries to request, and then add this functionality to request (already being discussed here). |
Related: #591 |
It would be great to see this made available. The lack of this makes Dredd difficult to use behind our company proxy. |
This is going to be implemented 🎉 I'd appreciate if all of you commenting here (and adding @alex-glv from #591) could give me some pointers. Do you think this kind of support would be sufficient to fulfill your dreams? 🙂 |
Support for HTTP(S) proxy has been implemented in Dredd v3.3.0. See documentation on how to use it. |
…ompiler (#51) New Fury adapter for parsing API Blueprint uses Drafter NPM, which decides whether to use C++ version or JS version of Drafter. This way, Dredd Transactions should become installable also on machines without C++11 compiler.
it doesn't appear that dredd leverages http_proxy or https_proxy when doing it's web calls to the API endpoint.
The text was updated successfully, but these errors were encountered: