Re: LWP posting

Replies are listed 'Best First'.
Re^2: LWP posting by PerlSufi (Friar) on May 14, 2013 at 19:59 UTC
changing the crawler to use WWW::Mechanize for my sites gave me this error: `Error GETing https://prodp1.usps.com/adminweb/view.htm?requestPage=P1D +ASHBOARD: Can't connect to prodp1.usps.com:443 (certificate verify failed) at ac +s_get.pl l ine 44.` [download] I think I may need to use LWP instead. Maybe with HTML::Form? And actually, I should mention that I use mechanize to login. Just haven't had much success navigating with it because of js stuff	[reply] [d/l]
Re^3: LWP posting by Anonymous Monk on May 14, 2013 at 20:20 UTC
... certificate verify failed ... That's like a FAQ item having to do with HTTPS "certificate verify failed" error while trying to connect to https:// site using use WWW::Mechanize, "certificate verify failed" difference between Perl 5.14 and 5.10 Also, mechanize is lwp	[reply]
Re^4: LWP posting by PerlSufi (Friar) on May 14, 2013 at 20:40 UTC
Thanks for the insight, although.. I'm not sure what that means I need to do to mechanize for it to work.. I'll read on	[reply]
Re^2: LWP posting by PerlSufi (Friar) on May 14, 2013 at 21:27 UTC
Hi, Thanks for your insight. Actually, the header does say it is form encoded.. but how do I do that?	[reply]
Re^3: LWP posting by SnackySmorez (Initiate) on May 15, 2013 at 22:23 UTC
You can try forming your own url string and using url::encode. http://search.cpan.org/~chansen/URL-Encode-0.01/lib/URL/Encode.pod. Also worth checking out is uri::escape for %-encode and %-decode unsafe characters http://search.cpan.org/~gaas/URI-1.60/URI/Escape.pm	[reply]