Bug 818499

Summary:	The "Get the bits" navigation link in community page has redirected loop when click it after login.
Product:	OKD	Reporter:	yquan <yquan>
Component:	Website	Assignee:	Clayton Coleman <ccoleman>
Status:	CLOSED DUPLICATE	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.x	CC:	yujzhang
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-07 04:35:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description yquan 2012-05-03 08:44:42 UTC

Description of problem:
The get the bits page in community has redirect loop when click it after login.

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

How reproducible:
Always

Steps to Reproduce:
1.Login to the openshift website.
2.Go to the community page.
3.Click the GET THE BITS.
  
Actual results:
The page will go wrong with such message as below:

This web page has a redirect loop
The web page at https://openshift.redhat.com/app/logout has resulted in too many redirects. Clearing your cookies for this site or allowing third-party cookies may fix the problem. If not, it is possibly a server configuration issue and not a problem with your computer.


Expected results:
It can access to the GET THE BITS page correctly.

Additional info:

Comment 1 Clayton Coleman 2012-05-03 21:41:14 UTC

Did you clear your browser cookies?  If that fixes this, this is a duplicate of 817627

Comment 2 yquan 2012-05-04 02:17:25 UTC

When after click the "Get the bits",the whole openshift pages are can't access. And I cleared the cookies, the openshift website can access again, but click the button "Get the bits", the problem still occurring.

Comment 3 Clayton Coleman 2012-05-07 04:35:29 UTC


*** This bug has been marked as a duplicate of bug 817627 ***