Hope I understood everything. Up2date tells me, that I'm not registered. Trying to register fails, since rhn_register won't use a proxy. Up2date could you a proxy. Is it right, that you broke up2date (in using rhn) for users behind proxies ? It seems, that I have a valid RHn Account, but I can't use it without using rhn_register. Thanks.
*** Bug 18817 has been marked as a duplicate of this bug. ***
Can you please try specifying your serverURL in /etc/sysconfig/rhn/up2date as: http://your.proxy.here/https://www.rhns.redhat.com/XMLRPC And let me know if that works?
No it does not... Squid does not seem to handle the following request: 971196098.518 5 10.0.217.18 NONE/400 1123 POST /https://www.rhns.redhat.com/XMLRPC - NONE/- - As a quick try I added if string.find(self.__handler,"/http") == 0: self.__handler = string.replace(self.__handler,"/http","http") to xmlrpclib (line ?) just to discover that all does not work with ssl (POST is wrong. Should be CONNECT etc.) . If you use both with http it works. But it is really not nice. It seems that using ssl and proxy really needs a bit of work.
Assigned QA to jturner
Proxy support for both up2date and rhn_register is currently in the CVS versions and therefore will be rolled out in the next cut of the software made public.
*** Bug 22365 has been marked as a duplicate of this bug. ***
fixed in errata release, due out today.
is this actually fixed? I've set up both the proxy name and the authentication details and a netstat -a shows it still SSL'ing to 216.148.218.160 for the welcome message.
This is working for me. I ran 'rhn_register --config' and set attribute 2 to 'http:<proxy name>:<proxy port>' and set attribute 1 to 'yes' and that was all that it took.
I'm now getting 'unable to set up CONNECTION tunnel'. I didn't see any options as there are on up2date for setting my username and password for the authenticated proxy. I would suggest altering the comment for the rhn_register config. attribute 2 that says u must but the 'http://' in.
Created attachment 16004 [details] patch to rhn_register-1.3.2 to support proxy authentication
The above patch allows rhn_register to work through a proxy with authentication, I've only tested it with authentication on.
this patch will be included in a future errata release of rhn_register.
we used to fix our bugs for free (hey bill..... is that you out there ??? do you own redhat too???) now you foist off beta garbage as a finished product.... re-invent a lesser wheel.... hey you make bill gates almost nice ! talking about rh 7.1..... 6.2 was more stable ! can't you say "whoops" and say "click here to update " ????