Closed Bug 179672 Opened 20 years ago Closed 16 years ago

Keychain on server remembers localhost name, not address


(Camino Graveyard :: History, defect)

Not set


(Not tracked)



(Reporter: andrew, Assigned: mikepinkerton)


User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021104 Chimera/0.6
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021104 Chimera/0.6

This one is not likely to crop up too many times, due to the uncommon
circumstances to find it. I use my powerbook for designing my website, hence I
call to test the code. The problem comes when I call a file
that is password protected, eg by an .htaccess file. 

When the page is called for the first time, Chimera remembers (through the
keychain?) the location as 
or if the computer has a domain name entry

Fine, no problem. But in my case, my computer moves location frequently, and
hence it's fully qualified host/domain name changes with it - if I try to serve
up that same password-protected localhost page again, but from a different
location, I get the error "the host cannot be found".
Chimera should be storing the address as or localhost or something,
not the hostname.

Reproducible: Always

Steps to Reproduce:
1. Call password protected file on (save password to keychain)
2. Move network location, or give your computer a different name
3. Call the same passwd-protected file on

Actual Results:  
-> host not found
(even though the file is on localhost)

Expected Results:  
to find localhost!
Andy, how do other browsers behave in this situation, such as Mozilla and IE?
I do very similar things, in that I do php/mysql/apache web development, and I
use a variety of dhcp, ppp and static addessses.  (I do not use .htaccess, but I
do use HTTP_AUTH to control database access).

Chimera stores the url address I enter as the bookmark:
page is stored as such.
page http://[edit] is stored as such.
Any bookmark is robust to name changes which occur with moving locations.


Assignee: sfraser → pinkerton
Ever confirmed: true
Summary: HTTP_AUTH on server remembers localhost name, not address → Keychain on server remembers localhost name, not address
Target Milestone: --- → Chimera1.1
Keychain bugs -> 1.2.
QA Contact: winnie → history
Target Milestone: Camino1.1 → Camino1.2
Passwords are stored by the domain visited, with no attempt to make guesses about what domains will continue to be equivalent or resolve to a specific IP address, as down that road lies madness. If you load, then it will be stored and retrieved for, so this is WFM.
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.