I ended up basically replacing this part of my code my $req = HTTP::Request->new(GET =>"https://$username:$password\@ qualysguard.qualys.com/msp/scan_report_list.php");
with ... system "wget --proxy=on http_proxy=http://10.10.10.10:9090/--proxy-user=$proxyuser --proxy-passwd=$proxypass --user=$username --password=$password -O $SCAN_REPORT_FILE https://qualysguard.qualys.com/msp/scan_report_list.php";; if ( ! open INFILE, "<$SCAN_REPORT_FILE") { die "Could not open file ($!)"; } my $content; for (<INFILE>) { $content .= $_; } ... Its not elegant, but it got the job done. They guy I wrote this for ended up not using it because I had hacked the original perl from Qualys too much by using wget and he was afraid that Qualys and the other CMS (Content Management Solution vendor in Kansas City) would not support it. (forgot to copy [email protected] on the first reply so I added them back in just in case someone else has some additional input) - daryl On Mon, Dec 7, 2009 at 1:57 PM, Scott, James M Dr <[email protected]>wrote: > No, I’ve just run into a situation where internal proxy server now asks for > authentication and I couldn’t get it to work. > > I saw your thread and it did not look promising. I saw the same results. > > > > *From:* Daryl Fallin [mailto:[email protected]] > *Sent:* Monday, December 07, 2009 2:41 PM > *To:* Scott, James M Dr > *Subject:* Re: [Kc] Perl LWP (libwww-perl) problems using a proxy that > requires > > > > No. I couldn't resolve the issue as I remember and just moved on and ended > up using some perl to call wget to retrieve the appropriate data. > > Do you have an idea or fix for the problem? > > On Mon, Dec 7, 2009 at 9:40 AM, Scott, James M Dr <[email protected]> > wrote: > > Daryl, did you ever get this problem solved? > > The message thread simply ends without resolution…. > > >
_______________________________________________ kc mailing list [email protected] http://mail.pm.org/mailman/listinfo/kc
