311708 - Prefix "www" not automatically removed for sites that do not load with the prefix appended

Status: RESOLVED INVALID

(Firefox :: Address Bar, defect)

Description

[butlerj]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

some sites do not load with the prefix "www." ahead of the domain name. Rather
than removing the www. prefix and attempting to load the site again, Firefox
simply displays a "server not found" error.  However, when the prefix is removed
manually the site loads without a problem.

Reproducible: Always

Steps to Reproduce:
1.go to http://kamiki.net
2.change to http://www.kamiki.net and reload the site
3.
Actual Results:  
"server not found" error

Expected Results:  
when it could not find the site with the "www." prefix added, it should have
automatically tried to reload the site without the prefix or vice versa.

This bug affects every verson of Firefox I have used on Windows. I have not used
the Macintosh or Linux version enough to know if the bug exists there or not.

Comment 1

[butlerj]

Prefix "www" not automatically removed for sites that do not load with the
prefix appended

Comment 2

[u63580]

Your example URL does resolve via DNS, so of course FF should try to load the
page.  I get a timeout both with and without "www."

Comment 3

[Aaron Racine]

Reporter, are you still having this problem with the latest version of Firefox?

If you're still having problems with this, you'll need to provide a domain that doesn't resolve the "www" hostname.  As pointed out in comment #2, both hostnames you provided in the STR resolve via DNS.

Comment 4

[Samuel Sidler (old account; do not CC)]

The only time this wouldn't work is if the site had two sites setup via DNS (the non-www one setup incorrectly, but just correctly enough so Firefox gets told a site exists, and not forwarding to the www one). That'd be a server configuration probably, not an issue in Firefox.

Closing this bug as INVALID.