Closed Bug 249329 Opened 20 years ago Closed 19 years ago

password manager loses password on same domain

Categories

(SeaMonkey :: Passwords & Permissions, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: marcel, Assigned: dveditz)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 I have some basic authentication directories on my domain. All pages have different page titles (first thought that this could result in this problem). My pages are stored in http://mydomainhere.com/protected/page1 , /page2, .. I can use password manager to store password for /page1. As soon I access /page2 I enter the username/password combination for /page2. When I want to return to a bookmark of /page1, the basic authentication login masks pops up and asks me again for username and password and has an unchecked checkbox for storing the password. I haven't made much tests on this. I think it might be a problem with subpages on the same domain. Reproducible: Always Steps to Reproduce: 1. See details 2. 3. Actual Results: Problem in details described. Expected Results: Save the login information correctly.
I also want to mention that there might be a general problem with the identities. Sometimes it happens (when I start mozilla) that the identity selection menu appears (even I only have ONE identity). I then have to open the task manager, terminate process mozilla.exe and restart mozilla from scratch. The identity selection does not appear anymore and mozilla starts normally with my profile. Maybe this problem could lead to the described password manager problem?
Dup of bug 153986? Reporter: Please provide a sample URL where this happens. Re. comment 1: That's unrelated.
Blocks: 251959
No longer blocks: 251959
Blocks: 251959
No longer blocks: 251959
Product: Browser → Seamonkey
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.