Re: Forcing LWP-UserAgent to use a proxy server without modifying code

Reading the LWP::UserAgent documentation, you will find that $ENV{HTTP_PROXY} is only evaluated if you call the $ua->env_proxy method. You can either modify your code or modify (say) LWP/UserAgent.pm so that the ->new constructor automatically calls env_proxy.

Comment on Re: Forcing LWP-UserAgent to use a proxy server without modifying code Select or Download Code

Replies are listed 'Best First'.
Re^2: Forcing LWP-UserAgent to use a proxy server without modifying code by mvaline (Friar) on Jan 04, 2008 at 18:55 UTC
I successfully modified the source to LWP/UserAgent as you suggested. Line 98 of the version of UserAgent.pm that I have calls the env_proxy method if the correct parameter has been passed to it. I simply modified it so it always calls the method. Thanks!	[reply]
Re^3: Forcing LWP-UserAgent to use a proxy server without modifying code by Old_Gray_Bear (Bishop) on Jan 04, 2008 at 19:24 UTC
Umph. And the next time you get a New version of LWP from CPAN? What happens to your change on line 98, then? Hand-editing CPAN modules is a chancy proposition at best. You are setting yourself up to strange bugs in the future; and, what have you just done to the other folks using LWP::UserAgent? Suddenly their code breaks because they aren't using a proxy...? Also, is this code going to be run on other machines? Are you going to make the change to line 98 everywhere? Sigh. I'd strongly suggest that you rethink this policy. Make a local copy of LWP::UA in your ~home directory and edit that if you have absolutely to. Changing the universal copy of a CPAN module -- this is just Not A Good Idea. ---- I Go Back to Sleep, Now. OGB	[reply]
Re^4: Forcing LWP-UserAgent to use a proxy server without modifying code by Massyn (Hermit) on Jan 05, 2008 at 07:59 UTC
Sure, LWP::Simple is nice and easy, and gets the job done, but there's been many cases where I've had to change to the regular LWP, just because ::Simple is, well, too simple... Take the plunge - move onto LWP.. It's a lot more flexible...	[reply]