"www" not added automatically to sub-dowain webpages when typed in URL bar

VERIFIED INVALID

Status

Camino Graveyard
General
--
enhancement
VERIFIED INVALID
12 years ago
12 years ago

People

(Reporter: william brawley, Unassigned)

Tracking

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060911 Camino/1.0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.7) Gecko/20060911 Camino/1.0.3

I have found that whenever typing a URL in Camino in the form xxxxx.zzz, Camino will automatically add the "www" to the beginning.  However, whenever I type a URL in the form yyyyy.xxxxx.zzz, the "www" part is left off, sometimes resulting in a "Failed to Connect" error.  Could this feature be added?  Safari has it, and it is very convenient.

Reproducible: Always

Steps to Reproduce:
1.type a url such as "oit.gatech.edu"
2.Will get Fail to Connect error
3.adding "www" will then connect to site

Actual Results:  
The problem occurrs as described

Expected Results:  
automatically add "www" to beginning of URL to connect to site

Comment 1

12 years ago
This is a server misconfiguration (usually, although I suppose some server admins would argue that it's intentional) and fairly common. I'm of the opinion we shouldn't be trying to fix this, as it's perfectly legitimate for www.example.com and example.com to be two different sites altogether. If the admins think the two sites should be the same, then they should be setting up the server to do that, and if they aren't, it's not our problem.

cl
We only add www. automatically when using fixup on a non-keyword term that has no TLD; everything else is happening on the server side.

bob would get fixed up to www.bob.com
bob.com would not change, and it's the bob.com server's responsibility to point you to www.bob.com instead if bob.com was not a webserver.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID

Updated

12 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.