Red Hat Bugzilla – Bug 482831
send X-RHN-Transport-Capability of the proxy's rhnlib, not the clients
Last modified: 2013-01-10 05:01:24 EST
When proxy forwards a request to hosted, it passes along the clients http headers, which is generally good, but for X-RHN-Transport-Properties, we want those that the proxy supports (for http redirect support), not those of the client.
The header is actually X-RHN-Transport-Capability.
[15:54] <msuchy> jbowes: if I understand it correctly I should set X-RHN-Transport-Capability to follow-redirects=2, and nothing else (since proxy already understood redirects) to implement? Correct?
[15:54] <jbowes> msuchy: the version should be 3, since 2 was for the last implementation
So we should add to rhnBroker:
I wonder if broker is enough or I should add it to rhnRedirect as well...
Additionally the proxy will give this TB when redirecting:
Exception Handler Information
Traceback (most recent call last):
File "/usr/share/rhn/proxy/apacheServer.py", line 55, in __call__
ret = f(req)
File "/usr/share/rhn/proxy/apacheHandler.py", line 337, in handler
ret = handlerObj.handler()
File "/usr/share/rhn/proxy/redirect/rhnRedirect.py", line 83, in handler
status = self._serverCommo(self.req.read()) # part 2
File "/usr/share/rhn/proxy/rhnShared.py", line 207, in _serverCommo
File "/usr/share/rhn/proxy/redirect/rhnRedirect.py", line 127, in _handleServerResponse
redirectStatus = self.__redirectToNextLocation()
File "/usr/share/rhn/proxy/redirect/rhnRedirect.py", line 212, in __redirectToNextLocation
redirectStatus = self.__redirectToNextLocationNoRetry(loopProtection)
File "/usr/share/rhn/proxy/redirect/rhnRedirect.py", line 309, in __redirectToNextLocationNoRetry
File "/usr/lib/python2.4/site-packages/rhn/connections.py", line 193, in connect
File "<string>", line 1, in connect
TypeError: an integer is required
and values are:
Frame connect in <string> at line 1
self = <class 'socket._socketobject'> <socket._socketobject object at 0xb7d1635c>
args = <type 'tuple'> (('content-xml.rhn.webdev.redhat.com', '2443'),)
The port is expecting to be number not string.
s/splitport/splitnport/ in rhnShared should fix this issue.
Commited as f8b7351ca077bf64df4ef54783e16dfa3e5947f4
Keeping MODIFIED pending final confirmation on Akamai roll-out.
Mass moving ON_QA
1. Make sure that Akamai support is switched on on hosted (F-Akamain on webqa, real Akamai on stage)
2. register Satellite Proxy to hosted
3. register client to Satellite Proxy from step 2
4. confirm, that you are able to install package(s) on client from step 3
OK. The flag follow-redirects has been removed by commit
The flag was removed only in vader branch. Not in master, so it should be set up and working in recent versions. I.e in
spacewalk-proxy-0.7.2-1 and in spacewalk-proxy-0.8.1-1 as well.
An advisory 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 therefore 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.