Description of problem:
Customer reports that when trying to bulk download the upgrade packages from the Red Hat Network site, the "download" button just don't respond at all. Tried both IE8 and firefox but without any luck.
I've tested this and can reproduce the problem - on System -> Software -> Packages -> upgrade page and Channels -> Packages page. If I select 50 packages, clicking download button throws me back on the same page. If I select 12 packages, clicking the download button proceeds to the download confirmation page as expected.
Version-Release number of selected component (if applicable):
Red Hat Network 5.2.1
Steps to Reproduce:
1. Login to RHN -> Systems -> select system -> Software tab -> upgrade tab -> select all the packages (e.g. 1 to 20 of 300 (300 selected)
2. Click on Download Packages button
3. Try another page with the Download button, such as Channels -> Packages, select about 50 or a few hundreds and click on Download Packages button.
It does not respond or throws back on same page without proceeding.
Proceeds to download confirmation page to download pkgs.
For customer, if they go to Your Preferences -> RHN List Page Size and select highest entries per list page, then try to download packages e.g (1 to 50 of 300 (50 selected)) -> Click on Download Packages, it works.
For me, this does not make a difference. If the selection is larger than 40-50 packages, it does not work, otherwise, it works as expected.
*** Bug 596825 has been marked as a duplicate of this bug. ***
*** Bug 486414 has been marked as a duplicate of this bug. ***
*** Bug 464062 has been marked as a duplicate of this bug. ***
*** Bug 437779 has been marked as a duplicate of this bug. ***
The download package tarball facility has been rewritten so that it no longer involves redirects with enormously long URLs, which sooner or later would get cut off in user's browsers. Having said that, the 25 package per download tarball limit still applies, and the efforts have been made to present that information correctly to user.
*** Bug 473064 has been marked as a duplicate of this bug. ***