> Most excellent! Does it understand proxy environment variables?
> Someone using POE::Component::Client::HTTP needs to hop their
> firewall, so I can point them at your module if it does that.
The component is derived from LWP::UserAgent, so it is supposed
to have the same support for proxy environment variables. There
is a LWP::UserAgent::env_proxy method:
(quote from LWP::UserAgent manpage)
$ua->env_proxy()
Load proxy settings from *_proxy environment variables. You might
specify proxies like this (sh-syntax):
gopher_proxy=http://proxy.my.place/
wais_proxy=http://proxy.my.place/
no_proxy="localhost,my.domain"
export gopher_proxy wais_proxy no_proxy
Csh or tcsh users should use the setenv command to define these
environment variables.
On systems with case-insensitive environment variables there exists a
name clash between the CGI environment variables and the HTTP_PROXY
environment variable normally picked up by env_proxy(). Because of
this HTTP_PROXY is not honored for CGI scripts. The
CGI_HTTP_PROXY environment variable can be used instead.
(end of quote)
So if after calling $ua=POE::Component::Client::UserAgent->new you
call $ua->env_proxy, the component should understand those variables.
> You upload the module to your CPAN directory and follow the docs/form
> for requesting an entry in the modules list. The POE::Component
> namespace is sort of a free-for-all so people can contribute without
> me having to coordinate everything.
>
> Ahm... I think I documented why POE::Component exists in its manpage.
It's been a while since I read it. If I hear from CPAN before Monday
night, I'll upload the module, otherwise we'll have to wait for a
month or more, as I'll be out of the country.
Kirill
