Hi all, been searching for a while but am still stumped here. Wonder why some urls require the “www” tag, whereas other urls work fine just by [url]http://myname.com[/url]
@David_HarrisonMay 19.2005 — #Our ideal scene is one where non-specialized sites accept traffic on the www host name, but silently redirect it to the bare domain name. This is what no-www calls Class C. However, any site that takes in traffic one way or the other on both the www host and the bare domain are acceptable here.[/quote]Heh, I do exactly the opposite of that on my site. IMO without the www. the domain just looks naked.
@CharlesMay 19.2005 — #Heh, I do exactly the opposite of that on my site. IMO without the www. the domain just looks naked.[/QUOTE]And just what's wrong with naked?
@Stephen_PhilbinMay 19.2005 — #I really can't say I'm arsed what someone accesses by. I really can't imagine why someone would be so petty as to fuss over it.
If you'd have asked me which I would have thought more sensible, with "www." or without, I'd say definitely with the "www.". It is supposed to be a uniform resource locater afterall.
Use the hypertext transfer protocol to look on the world wide web for a domain named mycomain.com and ask for a file from its images directory called dangermouse.png
Use the hypertext transfer protocol to look for a domain named mycomain.com and ask for a file from its images directory called dangermouse.png. The domain might be on the world wide web, or it might be in the freezer in the butchers down the road. I know where, but some people think that providing explicit information is bad so I'm not going to tell you.
@NogDogMay 19.2005 — #Actually, the "www." is functionally a subdomain. You parse it from right to left if going from broadest to narrowest category.
com = one of several top-level divisions of internet domains
mydomain = the specific domain you've registered within the .com category
www = the specific logical server at mydomain.com you want to process HTTP requests.
You can call your default web server "bob" (bob.mydomain.com) if you want, but should have aliases/configurations so that http://www.mydomain.com and http://mydomain.com both direct HTTP requests to that primary web server.
@Stephen_PhilbinMay 20.2005 — #Ahhhhhh right. Makes a bit more sense looking at it that way round. I still don't get why having a world wide web subdomain is a bad thing though.
@ray326May 20.2005 — #I still don't get why having a world wide web subdomain is a bad thing though.[/QUOTE] I think the guy's secondary gripe is bandwidth consumed by the extra four characters. Considering there's a lot more to even an HTTP request than the URL, I think it's a bit of a nit-pick.
@felgallMay 22.2005 — #www is actually supposed to be the "machine name" which goes on the front of the domain name or sub-domain name. In practice many domains are configured to work either with or without it while the cofiguration for sub-domains that is part of the same hosting account does not usually cater for it being there.