Take an incoming GET request and check if the content is available from the edge network. If not start the download. If it is, issue an HTTP 302 redirect request to the client specifying the edge network URL.
Set Up: 1. Fixed the up2date client(rlx-2-04)bug for the 302 redirect with misa's help. 2. wrote queries to extract package redirect location with respect to pkg_id from the Location tables(rhnLocation, rhnPackageLocation & rhnPackage). 3.wrote a wrapper function which gets the package remote location path querying the db.If not available returns empty string. 4. Included the 302 code and included the redirect logic in the apacheRequest where it check for the availabllity of the package in the location table and if available, issues redirect request to the dummy http serevr(Akamai).Otherwise downloads the package from hosted(satellite as hosted). 5.Client Successfully downloads package from Https server(Akamai) afetr being redirected by the Hosted to Akamai. Conclusion: - Hosted receives the GET request from the client. - checks if the pkg available on edge network url(Akamai)[queries db] - if not,downloads pkg. - else issues a 302 redirect request to client with redirect path as Akamai. - Client now issues GET to akamai,checks SSL Cert handshake - finally downloads the package from Akamai.
bperkins will be the QA contact for ISO/package redirect when (if?) it is implemented
This bug has been closed due to inactivity. Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.