| Subject: | BUG: Ignores https_proxy environment variable |
| Date: | Wed, 20 Oct 2010 01:37:14 -0700 |
| To: | <bug-WWW-Salesforce [...] rt.cpan.org> |
| From: | "Duncan Graham" <DGraham [...] saba.com> |
Hi,
I'd like to report a bug. I have a fully functional piece of code
written using the WWW::Salesforce::Simple library. However, this is
running on a Virtual Machine. When I moved this virtual machine into my
laboratory (behind a proxy) it fails. After some research I found I
needed to create an environment variable called "https_proxy" for perl
to be able to operate https over a proxy. However, when using the ->new
command for the salesforce.pm the proxy denies the request.
Further inspection of the request showed that the salesforce.pm was
actually trying to send the request to the proxy url rather than to the
salesforce url VIA the proxy. The proxy was, hence, rejecting a request
to connect to itself via itself.
To replicate:-
Create a very simple salesforce script that just needs to execute the
->new command successfully.
Run this script without a proxy.
Set up a proxy on another machine.
Create an environment variable on the per machine called "https_proxy"
and give it the value http://xxx.xxx.xxx.xxx:nnn (substitute as
applicable).
Run this script again... the proxy request will fail and the proxy logs
will show that the perl script was requesting the proxy hit itself.
Notes:-
I think this should only require a small tweak to the salesforce.pm to
make it proxy aware. Otherwise, a small tweak to allow a proxy parameter
to be passed with the username and password at the start
I would have written the fix myself and submitted it with this, but I
haven't got as far as working out how to build .pms yet J
Rgds
Duncan
Duncan Graham
Support Engineer, EMEA
Saba
Circa, The Ring, Bracknell, RG12 1AA
tel: 00800 CALL SABA
Saba. Power Up Your People.
Show quoted text
_______________________________________________
People 2010 - Saba Global Summit | November 1-4, 2010 | Register Here
<http://www.sabapeople.com/registration.html>
_______________________________________________
This message contains information which may be confidential and
privileged. Unless you are the addressee (or authorized to receive for
the addressee), you may not use, copy or disclose to anyone the message
or any information contained in the message. If you have received the
message in error, please advise the sender by reply e-mail
dgraham@saba.com <mailto:dgraham@saba.com> , and delete the message.