up2date from behind corporate firewall

[Noah Silva [Mailing list]]

On Thu, 16 Oct 2003, David Juran wrote:

> M A Young wrote:
>
> > Currently the proxy settings are ignored for non-rhn up2dates.  If you are
> > logged in as root, a work around is to set the http_proxy environment
> > variable to point at your proxy.
>
> setting the http_proxy environment variable only takes me part of the
> way. I've reported this bug in
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107036 a coupple of
>...
> internal DNS, which fails.

Our internal DNS does lookups from the outside DNS, so it should work, but
it appears to just not be querying the proxy.  I tried using the quites as
a previous poster suggested, still no go.

Interestingly, the 2.1.1 rhn-applet DOES work with the proxy.  I can see
there is an update for up2date now, so maybe I should grab that with a web browser,
and try again.

snip of error:
  File "/usr/share/rhn/up2date_client/repoBackends/urlUtils.py", line 98,
in open_resource
    return opener.open(request)
  File "/usr/lib/python2.2/urllib2.py", line 328, in open
    '_open', req)
  File "/usr/lib/python2.2/urllib2.py", line 307, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.2/urllib2.py", line 824, in http_open
    return self.do_open(httplib.HTTP, req)
  File "/usr/lib/python2.2/urllib2.py", line 809, in do_open
    raise URLError(err)
urllib2.URLError: <urlopen error (110, 'Connection timed out')>