Bug 88612 - RHN requires repeated logins after downloading
Summary: RHN requires repeated logins after downloading
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chip Turner
QA Contact: Red Hat Satellite QA List
URL: https://rhn.redhat.com/network/errata...
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-11 13:22 UTC by Bill Greene
Modified: 2007-04-18 16:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-04-14 15:58:13 UTC

Attachments (Terms of Use)

Description Bill Greene 2003-04-11 13:22:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
After downloading a package, I hit the back button to download additional 
components (e.g., glibc-common and glibc, or the multiple packages for 
Samba).  I am asked to log in again.  After logging in, I am on the correct 
page.  This appears to only happen if I do a download -- if I just look at the 
page, then hit back, it works correctly.  I am using IE 6.0 on XP 
Professional.  Cookies, JavaScript, etc., are all on.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Link from RHN errata alert e-mail; log in and get details page.
2. Click on Packages link, then select a specific RPM.
3. On the RPM page, click the download link.  The package downloads.
4. Click the browser "Back" button.

Actual Results:  I am on the "Please Sign In" page.  The URL is correct.  Once 
I log in, I am on the correct page (i.e., the Packages page).

Expected Results:  I would be on the Packages page without having to sign in 

Additional info:

Comment 1 Chip Turner 2003-04-14 15:18:30 UTC
this should now be fixed, can you test it again?

Comment 2 Bill Greene 2003-04-14 15:42:48 UTC
It's working now.  Thanks!

Comment 3 Josef Komenda 2003-04-14 15:58:13 UTC
Works, closing.

Note You need to log in before you can comment on or make changes to this bug.