Re: [Soaplite-devel] using SOAP::Lite client utilizing firewall proxy

[Thomas J. P. <Tho...@sx...>]

On 03/20/2011 08:58 AM, Sean Case wrote:
> We have a firewall and the preferred method is to go through a proxy to
> get out. I have tried this:
> $api->transport->proxy(http => $proxy); which yielded: FATAL ERROR::
> proxy: transport protocol not specified
>
> I have also tried other variations (as found at
> http://cookbook.soaplite.com/ and also in the SOAP::Lite PODs) which get
> the same result.
>   Also, I have tried: $ENV{'HTTP_proxy'} = $proxy; which got: FATAL
> ERROR:: 500 Connect failed: connect: Connection refused; Connection
> refused at...
>   so that appears to not even be setting it (our firewall doesn't seem
> to be acknowledging the proxy when I use this). The admins have tested
> out the firewall to check that it will actually pass through to the
> correct endpoints and they can't see the script even hitting the proxy.
> I have been searching around and I haven't found any examples where
> someone has tried this and succeeded, so I'm not sure what the root
> cause is. Any assistance would be greatly appreciated.

SOAP::Lite uses LWP::UserAgent, so its proxy configuration applies.

My SOAP::Lite clients do something like:

|    if ($ENV{http_proxy}) {
|        $soap->proxy($endpoint, $timeout, env_proxy => 1);
|    } else {
|        $soap->proxy($endpoint, $timeout);
|    }

Note that the environment variable name is "http_proxy" (all lower-case) 
and not "HTTP_proxy".

-- 
Thomas J. Pinkl
Senior Systems Architect
Health Business Systems, Inc. (An SXC Company)
738 Louis Drive
Warminster, PA 18974
T: (215) 491-0763
    (800) 444-1427
F: (267) 280-5101
http://www.HBSRx.com/


This communication, including any attachments, may contain information that is confidential and may be privileged and exempt from disclosure under applicable law. It is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender. Thank you for your cooperation.