This support is already there. We need to verify that it works. The biggest pain in all this will be setting up a test environment. I'll work with Akamai to get access to test servers.
This capability has been added in the rhnlib module which acts as a gateway between the client(up2date/satsync) and hosted/akamai edge-nwk. Basically the rpclib is modified such that the fail-over and redirect are handled at the same place. Implemented Flow: - when you run up2date it starts with POST and GET request for login and pkg hdr info respectively - for every package a GET request is sent to hosted . - hosted redirects with 302 back to the client with akamai url - client sends a request to akamaized url for pkg. - we fill the headers with pkg info and redirect paths for akamai use in case of failure or redirect. - if package avaiable: downlods it - elif 4xx or 5xx from akamai: #send the request back to hosted, set no-redirect flag (avoid loops) #download pkg - elif 302 from akamai: #sends a 302 back to the redirect url and if hosted downloads the pkg.
summary changed to properly reflect what package got modified
It was decided that the client portion of the ISO Pkg Redirect should be deliver with with the RHN-RHEL3.8 and RHN-RHEL4.4 update agent release
RHN Dev and RHN QA have agreed to develop and test this bug
Moving component to RHEL for errata reasons. Note that the server side bits for 302 are not going into 410, they will be turned on at a later point. Testing right now should be regression testing.
This bug has been fixed in this release
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 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/RHEA-2006-0470.html