# Proxy question when using soap/wsdlDriver

**URL:** <https://www.ruby-forum.com/t/proxy-question-when-using-soap-wsdldriver/86041>\
**Category:** Ruby\
**Created:** [March 23, 2006, 4:49pm UTC](https://www.ruby-forum.com/t/proxy-question-when-using-soap-wsdldriver/86041 "2006-03-23T16:49:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jared\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/a4c791/32.png) [@Jared\_R](https://www.ruby-forum.com/u/Jared_R)\
**Post date:** [March 23, 2006, 4:49pm UTC](https://www.ruby-forum.com/t/proxy-question-when-using-soap-wsdldriver/86041/1 "2006-03-23T16:49:36Z")

</div>

Hi all,

I’m going through the Brian M. web services article  
([http://www.testing.com/writings/behind-the-screens.pdf](http://www.testing.com/writings/behind-the-screens.pdf)), but at my day  
job  
I’m behind a proxy/firewall.

To run a Ruby gem I have to do something like this

gem install -p http://proxy\_box.com:80 rails

but I’m having a bit of trouble finding the equivalent for the soap  
code.  
I’m trying to run within IRB but can switch over to “real” Ruby code in  
a  
file if it makes it easier.

specifically, I’m trying to run this code:

require “soap/wsdlDriver”  
wsdl = “[http://api.google.com/GoogleSearch.wsdl](http://api.google.com/GoogleSearch.wsdl)”  
factory = SOAP::WSDLDriverFactory.new(wsdl)

At this point, the factory can’t create the factory because it can’t  
“see”  
outside the web proxy. I can download the wsdl file (via a web browser)  
and  
save it, but then I won’t be able to actually exercise the web service.

So how do I tell Ruby (or IRB or the soap code) to use a proxy?

Thanks all!

Jared

---

<div class="post-metadata">

**Author:** ![Jared\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/a4c791/32.png) [@Jared\_R](https://www.ruby-forum.com/u/Jared_R)\
**Post date:** [March 23, 2006, 4:57pm UTC](https://www.ruby-forum.com/t/proxy-question-when-using-soap-wsdldriver/86041/2 "2006-03-23T16:57:51Z")

</div>

I had a similar problem and ended up setting an env variable:

http\_proxy=http://URL:PORT

The SOAP connection worked after that, but mileage will vary.

-Dave