ASPN ActiveState Programmer Network
ActiveState
/ Home / Perl / PHP / Python / Tcl / XSLT /
/ Safari / My ASPN /
Cookbooks | Documentation | Mailing Lists | Modules | News Feeds | Products | User Groups


Recent Messages
List Archives
About the List
List Leaders
Subscription Options

View Subscriptions
Help

View by Topic
ActiveState
.NET Framework
Open Source
Perl
PHP
Python
Tcl
Web Services
XML & XSLT

View by Category
Database
General
SOAP
System Administration
Tools
User Interfaces
Web Programming
XML Programming


MyASPN >> Mail Archive >> activeperl
activeperl
Re: Problems with PPM - SOLVED
by Gisle Aas other posts by this author
Oct 16 2009 3:07PM messages near this date
RE: Problems with PPM - SOLVED | Help with DBI to get HDD size of C drive of remote PC running MS-SQL Express 2005
On Oct 16, 2009, at 23:01 , Henry Hartley wrote:

>  Henry Hartley wrote:
> >>>>>> There is something preventing LWP from seeing your
> >>>>>> http_proxy environment variable.  The error message
> >>>>>> doesn't even come from PPM itself, it is
> >>>>>> LWP::UserAgent::proxy() that is complaining
> >>>>>> about "10.1." not being a valid proxy address.
> >>>>>>
> >>>>>> You may want to write a small test program using
> >>>>>> LWP::simple to download a file from the web and see
> >>>>>> if you run into the same issue.
> >>
> >> This four line script will generate the error for me.
> >>
> >> #!/usr/bin/perl
> >> use LWP::UserAgent;
> >> $ua = LWP::UserAgent->new();
> >> $ua->env_proxy;
> >>
> >> C:\temp>lwp.pl
> >> Proxy must be specified as absolute URI; '10.1.' is not at
> >> C:\temp\lwp.pl line 4
> >>
> >> The error message is exactly the same (i.e. the 10.1. doesn't
> >> change) no matter what I set http_proxy to or if it is not set at
> >> all. Does capitalization of the http_proxy matter and if so,
> >> what's proper? Otherwise, I'm lost.
> 
>  There was an environment variable called RSYNC_PROXY which was set  
>  (for some unknown reason) to "10.1." When I removed that, all became  
>  well. Crazy.

Recent versions of libwww-perl do have a fix[1] for this.   
Unfortunately that only made it in libwww-perl-5.832 and ActivePerl  
1006 ships with 5.831.  If you manage to 'ppm upgrade libwww-perl' you  
should not risk having RSYNC_PROXY coming back to haunt you :-)

[1] http://github.com/gisle/libwww-perl/commit/e99048842090d3c7cc03cdb0beb590d5b97b531f

Regards,
Gisle

_______________________________________________
ActivePerl mailing list
ActivePerl@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Thread:
Henry Hartley
Wayne Simmons
Henry Hartley
Henry Hartley
Jan Dubois
Henry Hartley
Henry Hartley
Henry Hartley
Gisle Aas

Privacy Policy | Email Opt-out | Feedback | Syndication
© ActiveState Software Inc. All rights reserved