578963 - (jamesadrian) Goes to http://americanfreeenterpriseparty.org/ instead

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[James Adrian]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6

When I enter http://futurebeacon.com/ into the URL window, the browser goes to http://americanfreeenterpriseparty.org/ instead.  When I enter http://www.futurebeacon.com/ into the URL window, the browser goes to the correct address.  The inclusion of the www is oddly required.  http://americanfreeenterpriseparty.org/ is a URL I frequently go to.

Thank you for your help.

Jim Adrian
[e-mail]

Reproducible: Always

Steps to Reproduce:
1. Go to http://futurebeacon.com/
2. Go to http://www.futurebeacon.com/
3. Observe that the browser goes to two different places in step 1. and 2.


Actual Results:  
In my case, it goes to http://americanfreeenterpriseparty.org/ in step 1. and goes to http://www.futurebeacon.com/ in step 2.

http://americanfreeenterpriseparty.org/ is a URL I go to often.

Expected Results:  
The browser should go to the URL placed in the URL window.

This anomaly is absolutely consistent and repeatable.

This adversely impacts upon the value of futurebeacon.com if there are many people who use this browser in OSX.

Comment 1

[Matthias Versen [:Matti]]

http://futurebeacon.com/ and http://www.futurebeacon.com/ are different addresses. the last one is the subdomain www at the domain futurebeacon.com and both can be of course different from the first one.

In my case I get an empty site in both cases.
Please clear the disk cache under clear private data and try it again.

Comment 2

[James Adrian]

This bug was absolutely consistent until I reported it.  I suspect that requiring that I clear the cache in order to report the bug cleared the bug.  Now it is gone.

I don't understand how a large or full cache would make the browser go to a URL other than the one specified in the URL window, but I reported it as it happened.

Jim Adrian
[e-mail]

Comment 3

[Matthias Versen [:Matti]]

>I don't understand how a large or full cache would make the browser go to a URL
>other than the one specified in the URL window, but I reported it as it
>happened

I couldn't reproduce the redirect and I think that the page changed and you had  an old redirect in the cache that the page sent in the past.

marking wfm, please reopen if you get this again.