250962 - Fails to allow Sign on to MyNetscape.com

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[biz]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040626 Firefox/0.9.1

When clicking on the Sign-in link on MyNetscape.com, the browser appears to
bounce between redirects and then eventually Netscape.com issues an error. I can
signin correctly with Mozilla on this platform (Red Hat 8.0) but not FireFox
0.92. Yes, I do have a valid account on MyNetscape.com. 


Reproducible: Always
Steps to Reproduce:
1. Go to MyNetsacpe.com
2. Click on the Signin graphic
3. Watch the status bar to see the continual redirects until an error page is
returned

Actual Results:  
Just got an errpr page

Expected Results:  
Sent me through to the sign-on page. Note that I did not reach a sign-on page
where a user name and password are required.

Comment 1

[Chris Thomas (CTho) [formerly [e-mail] [e-mail]]]

WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a2) Gecko/20040710
and
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040711
Firefox/0.9.0+

There are definitely many redirects going on, but I get no errors.  Do you have
javascript disabled or cookies blocked?

-> Firefox General, it's not a problem with the Firefox website.

Comment 2

[biz]

I have checked that javascript is fully enabled and it is. 
I had imported cookies from Mozilla so I removed all cookies related to
MyNetscape and tried again. This time, I was able to get to the login page and
provide my username and password. After that, I got the same series of redirects
ending with the error page
http://my.screenname.aol.com/error.psp?error=220&siteId=mynscpPROD&continueUrl=/_cqr/login/login.psp%3FauthLev%3D0

Note that I am running Linux RedHat 8.0

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.