Closed
Bug 230168
Opened 21 years ago
Closed 21 years ago
DNS: lookups in Firebird will not use locally defined hostnames (i.e. ones defined in netinfo or /etc/hosts) when there is no internet connection available
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 194476
People
(Reporter: bertosmailbox, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031026 Firebird/0.7
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031026 Firebird/0.7
Hello,
I develop multiple websites on my powerbook and differentiate between them using
apache virtual hosts. I setup the hostname for that virtual host in netinfo to
point to 127.0.0.1, and then enter the URL in the browser:
http://personal/
http://client1/
http://client2/
When the machine is not on the network, these hosts do not work and firebird
returns an error similar to: http://www.google.com cannot be found.
I have similar results in mozilla, except the error there is:
http://<hostname>.com could not be found.
In mozilla, I tried offline mode, but it returns an error stating that the site
cannot be viewed offline.
The problem seems to be with FireBird / Mozilla because I'm able to view the
sites offline just fine using Safari. This proves to me that Apache and the
netinfo and/or /etc/hosts is setup properly.
Thanks!
Reproducible: Always
Steps to Reproduce:
1. Take the machine off the network
2. Setup a hostname in /etc/hosts or netinfo
For netinfo:
open up /Applications/Utilities/Netinfo manager
go to Machines
duplicate localhost
rename localhost copy to whatever
or in /etc/hosts, add a line:
127.0.0.1 whatever
3. Setup virtual hosts in apache
NameVirtualHost *
<VirtualHost *>
DocumentRoot /path/to/root
ServerName whatever
</VirtualHost>
Once you have the virtual host setup restart apache.
Quit out of Firebird
Open up Firebird
Try to access http://whatever/
Actual Results:
You see the error that www.google.com cannot be found and the site is not
accessible.
The site is accessible from Safari, though.
Expected Results:
Go to the virtual host as expected.
The two workarounds I have are:
Make sure the first virtual host entry is the site I'm working on and access it
via: http://127.0.0.1
or
Use Safari; it works as expected.
Summary: Firebird will not use locally defined hostnames (i.e. ones defined in netinfo or /etc/hosts) when there is no internet connection available → DNS lookups in Firebird will not use locally defined hostnames (i.e. ones defined in netinfo or /etc/hosts) when there is no internet connection available
Comment 1•21 years ago
|
||
my bad, I thought I'd pasted this in IRC for you, but I didn't
*** This bug has been marked as a duplicate of 194476 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
I think that "Internet Keywords" is intefering here. Try using about:config to
turn off "keyword.enable" (set it to false).
There are probably two problems here, but do that, it should at least make the
error message consisten w/ mozilla's results.
QA Contact: benc
Summary: DNS lookups in Firebird will not use locally defined hostnames (i.e. ones defined in netinfo or /etc/hosts) when there is no internet connection available → DNS: lookups in Firebird will not use locally defined hostnames (i.e. ones defined in netinfo or /etc/hosts) when there is no internet connection available
Also, could you clarify what you mean by "not on the network?"
Are we talking about dialup or LAN (ethernet/wireless).
Status: RESOLVED → VERIFIED
Disabling keyword lookup does change the error message. If I'm trying to access
the site foo, as defined in /etc/hosts (127.0.0.1 foo), the error tells me that
http://foo.com cannot be found.
In my case "not on the network" means:
- no airport
- no ethernet plugged in
- in an airplane on my way across the country
Thanks!
Yeah. This one has me somewhat stumped. I've been trying to read lookupd
documentation (which of cours is not mentioned at all in gethostbyname()'s man
pages), but I can't figure this out.
I did get as far as the following, which, if you could try might be useful.
type: "lookupd -q host"
Will display your lookupd hosts (including DNS) cache.
type: "lookupd -d"
then type: "hostWithName: localhost"
If it says NIL, then Mac OS X, for some reason, could not find your /etc/hosts
entry.
"lookupd -q host"
shows everything as expected. all the hosts are there in the cache.
"lookupd -d" ...
That also found the hostnames in /etc/hosts and even told me it found them there.
Looks like the Mac OS X side of things is working properly. Safari (and from a
post in another bug, other browsers) are all able to see hostnames defined in
/etc/hosts just fine.
berto: can you try a 1.6 or 1.7 based build (like Mozilla 1.6 or maybe a newere
Firebird daily build?
Looks like the problem is fixed in Mozilla 1.6, very cool!
I tried finding a nightly snapshot of Firebird for OS X here:
http://ftp.mozilla.org/pub/mozilla.org/firebird/nightly/
but was unable to find one. I'll test it out as well if you can point me to a
binary.
Thanks!
Looks like the problem has been resolved in Mozilla Firefox 0.8; awesome!
Thanks!
You need to log in
before you can comment on or make changes to this bug.
Description
•