283464 - FF forgets wrong realm when sending HTTP/1.0 401 Unauthorized

Status: RESOLVED EXPIRED

(Core :: Networking: HTTP, defect)

Description

[Martin Rasp]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

I have opened two different URLs (same server) protected by basic http
authentification in FF. When clicking onto the logout script of one URL which
sends an "HTTP/1.0 401 Unauthorized" then FF also forgets the http
authentification of the other URL. When accessing that URL I have to
authenticate again.

Reproducible: Always

Steps to Reproduce:
1. open URL "http://myserver/dir1/" which is protected by a realm "Dir1-Access"
(".htaccess" file in "dir1") in a FF window
2. open URL "http://myserver/dir2/" which is protected by a realm "Dir2-Access"
(".htaccess" file in "dir2") in a second FF window or tab
3. click onto a link (PHP-script) which sends "HTTP/1.0 401 Unauthorized" for
the "Dir2-Access" realm

Actual Results:  
FF forgets the http authentification for realm "Dir1-Access" and I have to
reauthenticate myself.

Expected Results:  
FF should only forget the http authentification for "TSM-Administration" and not
for "Dir1-Access"

Comment 1

[Martin Rasp]

(In reply to comment #0)
> Expected Results:  
> FF should only forget the http authentification for "TSM-Administration" and not
> for "Dir1-Access"
Please replace "TSM-Administration" with "Dir2-Access" ;-)

Comment 2

[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 3

[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.