Description of problem: An enterprise customer is requesting we allow him the ability to change the user-agent string generated by http(s) requests from up2date and rhnsd. This will allow him to allow up2date to pass through his restrictive corporate firewall unimpeded. My testing using Squid configured to log user-agent strings shows that up2date currintly generates *no* user-agent string when communicating with the server, and it's hard to filter/allow on nulls.
I've got a patch for this, will take a look for the next release.
No, the only time it doesn't send an user-agent string is when it does the CONNECT to the http proxy to forward the SSL connections. Also, this is an rhnlib bug, not an up2date one, so reassining there.
I seem to be cross my comments on this bug with another similar bug. Sorry. In addition, here is an rhnlib patch: --- rhnlib-1.3/rhn/connections.py.akl 2004-04-02 15:47:00.000000000 -0500 +++ rhnlib-1.3/rhn/connections.py 2004-04-02 15:47:29.000000000 -0500 @@ -154,7 +154,8 @@ userpass = "%s:%s" % (self.__username, self.__password) enc_userpass = string.strip(base64.encodestring(userpass)) self.putheader("Proxy-Authorization", "Basic %s" % enc_userpass) - + self.putheader("User-Agent", "rhnlib ssl connect") + class HTTPSConnection(HTTPConnection): response_class = HTTPResponse default_port = httplib.HTTPSConnection.default_port Theres a more sophisticated patch floating around, but I'm not convinces the extra code needed to make a configurable user-agent is worth it.
Patch got into rhnlib-1.7 How important is this to make a backport of it? Is handing them the newer packages "good enough"?
user configurable user-agent support is currently "notabug", and there are no currently no plans to add it.
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-375.html
This bug is against Red Hat Enterprise Linux 3. The errata mentioned only covers Red Hat Enterprise Linux 2.1 as far as I can tell. Will a seperate errata be issued?
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-382.html