Bug 804497 - Can not access app/getting _started page on website using firefox10.
Summary: Can not access app/getting _started page on website using firefox10.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 05:17 UTC by Yujie Zhang
Modified: 2015-05-15 01:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:34:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yujie Zhang 2012-03-19 05:17:48 UTC 
Description of problem:

Can not access app/getting _started page on website.

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

devenv-stage_146

How reproducible:always

Steps to Reproduce:
1.Go to Openshift website and login
2.Click the "Learn more" link on home page and click the "Read more about getting started" link
3.Click the "Express" link on the navigation bar and click the "Want to know more?
Read the Getting Started Guide" link 
  
Actual results:

After step 2 and step 3,I was redirected to the app/express page, not the app/getting_started page, even when I use the url of app/getting_started, I was also redirected to the app/express page.

Expected results:

The app/getting_started page should be accessible.

Additional info:
Comment 1 Yujie Zhang 2012-03-19 06:50:49 UTC 
This issue only happened on firefox10.
Comment 2 Fabiano Franz 2012-03-19 15:43:05 UTC 
This is probably browser cache for the redirection (we also ran into this issue during development). Could you clear/disable the cache and try again? Thanks!
Comment 3 Yujie Zhang 2012-03-20 03:00:37 UTC 
(In reply to comment #2)
Try on stage today, does not have this issue now, thank you!
Note You need to log in before you can comment on or make changes to this bug.