Closed Bug 252778 Opened 21 years ago Closed 20 years ago

checking aol mail requires 2 logons

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ny3ranger, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040707 Firefox/0.9.2 When checking aol mail through their website, most of the time requires 2 logons. First you log on and they say failure please try again and when you click on the link to try again, it works! Reproducible: Sometimes Steps to Reproduce: 1. go to www.aol.com 2. put in my username and password 3. get the error page and click on the link that says log on again, and instead of give you a log on page it suddenly works and goes into your mail Actual Results: It worked. Im just reporting the initial failure almost everytime it happens. Expected Results: Log on the first time around.
WFM on first try, 20040722 trunk PC/Win2000
Version: Trunk → 1.7 Branch
Product: Browser → Seamonkey
This is also true at Netscape.com (probably the same issue). If you have the browser set to notify you when you're leaving a secure page, it pops up 10 notices and the screen says "Signing out of Screen Name Service. Please wait . . . ", then says the service is unavailable. If you go back and go into Netscape mail again, it works (you are already signed in).
Tashfin Wahid, Do you see this with a recent build such as Mozilla1.7.6 ?
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.