An Internet or Web address (sometimes called a URL, or Uniform Resource Locator) typically is composed of four parts: • A protocol name • The location of the site • The name of the organization that maintains the site • A suffix that identifies the kind of organization it is (such as .com for a commercial organization) For example, the address http://www.Astahost.com/ provides the following information: http: This Web server uses Hypertext Transfer Protocol (HTTP). www: This site is on the World Wide Web. Astahost :The Web server is at Astahost. com :This is a commercial institution.

Reply

the 'www' is more or less just a subdomain...many websites don't even need you to add 'www' to work...

Reply

Yeah I think that the www is just from the past but soon you won't need it!
It's just something too long in the adress.. Just like the http......
It's just important if you are in the army

Reply

http://no-www.org/

That website shows you how to get rid of your www and explains why the www is no longer needed on the World Wide Web.

Reply

I think ill always put www in the url of a site, just from habit.

Reply

Actually, http: is needed, it defines the default port for that protocol to be used.

Your browser settings however or registry settings state that if it's not there, then it will include it as the default, unless you've change this setting.

It's only minimal speed difference.

Things that affect the speed can be proven by just typing the name astahost in the browser, this means your computer has to include http:// to the address as well as a forward slash / to the end of it, it could then go through a list of common domain endings like .com .net .org etc if it can't locate that name as it is or it would default to the search engine.

So when typing an address, use http://astahost.com/ for better performance, it could also be wise to use www incase they aren't class B.


Cheers, MC

 

 

 

Reply

Actually, you have more to an URL than you state here. You forgot the user identification section.

protocol://user:pass@subdomain(s).domain.toplevel./path/to/file

- protocol being one like http ftp irc ...
- user being your username when requesting access to that specific resource. If none specified, most User Agents (browsers for example..) will log in with username Anonymous or blank
- pass being the password you use to validate your user credentials. Defaults to a random email adress-like pass for most User Agents, like IEUser@ or just blank
- subdomain being the subdomain of the pc where the resource is. Defaults to www for HTTP, or blank
- domain being the name of your domain, which includes the toplevel (com, org, net, ...)
- path/to/file being the relative path to the resource you're trying to access. Relative towards the home path set by the server you're accessing to find the resource. On UNIX systems, this is Case Sensitive!

Mark that after the toplevel domain name there is a dot (.), this is the root domain. All domains most have it, yet, nowadays, this last dot is omited and implicitly presumed.

Reply

i dont uses www. BUT YOU NEED HTTP THATS A MUST that connects to the sever that hosted it but its no big deal

Reply

I have always tended to write both the www and the http just because it is more reliable. At least thats why i first did it, now i do it more out of habit.

Reply