Bug 88612

Summary:	RHN requires repeated logins after downloading
Product:	[Retired] Red Hat Network	Reporter:	Bill Greene <bill>
Component:	RHN/Web Site	Assignee:	Chip Turner <cturner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	RHN Stable	CC:	rhn-bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://rhn.redhat.com/network/errata/errata_details.pxt?eid=1543
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-04-14 15:58:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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:
Always

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 
again.

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.