Closed
Bug 275074
Opened 20 years ago
Closed 19 years ago
Cannot log in to secure site.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: gesteve, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041217 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041217 Firefox/1.0+ The Ameritradeplus site loads properly, but after entering account number and pin, this message appears: Unable to authorize access. Please try again. Contact Ameritrade Plus at 800-888-3999 if you continue to have difficulty accessing your account. Thank You. Reproducible: Always Steps to Reproduce: 1.Log onto Ameritradeplus (https://wwws.ameritradeplus.com/) 2.Enter account number 3.Enter PIN Actual Results: Access denied. Expected Results: Access to account should have occurred. There is no problem accessing Ameritradeplus using Netscape 7.1. I have downloaded and installed the latest update of Firefox. The problem still exists. The same problem occurs when attempting to log onto Bank of America. This site also loads properly with Netscape 7.1. Both are secure sites. The browser is set to accept all cookies. I thought I had submitted this problem earlier today, but when reviewing today's submissions, it wasn't there, and I have received no notification about the bug as has been the case in the past.
Comment 1•20 years ago
|
||
I have seen this behavior on Suse 9.1 with Firefox 1.0.1, and this URL: https://secure-support.novell.com/eService_enu/start.swe?SWECmd=Start
Comment 2•19 years ago
|
||
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 3•19 years ago
|
||
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•