

Read this answer in context đ 3 All Replies (8) Windows: "3-bar" menu button (or Tools menu) > Options > Advanced > Network mini-tab > "Settings" button Mac: "3-bar" menu button (or Firefox menu) > Preferences > Advanced > Network mini-tab > "Settings" button Is there anything in connection settings that would cause Firefox to bypass your operating system's internal DNS resolution? You can review that here: If you notice Firefox adding a (or whatever is specified in the various preferences whose names start with browser.fixup).ÄȘnyway, if www is getting added, you know that the DNS lookup failed. If you test again, do you get the anticipated DNS response? (3) Double-click the keyword.enabled preference to switch it from true to false. (2) In the search box above the list, type or paste keyw and pause while the list is filtered Click the button promising to be careful. (1) In a new tab, type or paste about:config in the address bar and press Enter. This is the keyword service and it can be disabled. If DNS returns with no A record, then what you entered will be submitted to your current default search service. When you submit something that contains no spaces on the address bar, Firefox typically will check DNS. After all this time, there is no excuse for not fixing it now.
HOST FILE FOR MAC CODE
Repair Firefox code so that it attempts to resolve the name BOTH on the web and in the hosts file before using the URL as a search term in the default search engine. Firefox disables this major feature of IIS, Apache, and any other web server that might exist.ÄŻirefox must not disable features of the web server. The only way that virtual hosting can work is if the virtual hosts have different names. Viewing the web site with the computer's IP address cannot possibly work, because all of the virtual hosts have the same IP address, which is the whole point of virtual hosting. Viewing a web site in the file system causes the links in the site to go to the computer's root, not the site's root. The operating system, the web server, the entries in the hosts file, and the user's typing skills are not the cause.ÄȘnyone using virtual hosting on their local computer for web development cannot test their sites with Firefox.

This is Firefox's behavior in OS X and in Windows, thus also in IIS and Apache. This is a problem with Firefox, not the local computer. Assuming that Firefox developers browse the web, they know about this problem and have willfully and negligently-and perhaps maliciously-ignored it for at least eight years. Even if the name appears in the hosts file and has been entered correctly, Firefox uses it as a search term in the default search engine. Firefox ignores the presence of the hosts file, never using it to resolve a URL.
