what does http stand for in web addresses? My best guess is Hyper Text um… Toilet Paper? Eh, I’m stumped on this one.
Also, why the colon and the two back-slashes?
hyptertext transfer protocol
Hyper Text Transfer Protocol
So what does that mean? Is it really necessary?
I know https is for a secure site… but does “http” actually do anything?
Yes, it tells the browser how to expect data to be transferred.
HTTP is the most common (and is the default if you don’t specify) but there are other.
HTTPS://
FTP://
gopher:// (are there any useful gopher servers still around)?
telnet://
Two slashes, not backslashes – only Windoze uses backslashes for anything except escape characters. My guess is that the syntax calls for two slashes after the protocol type and colon separator so as to avoid confusion with directory separators ("" in DOS/Win and “/” pretty much everywhere else).
They’re all protocols. That is, they’re all agreed standards for transferring data. The prefix tells your browser and any associated plug-ins (e.g. newsreader software for ‘news’ prefixes) what sort of connection is being made and what sort of data to expect [very loosely speaking].
If you’re feeling up to it, you can read the RFC’s for these protocols (RFC stands for “Request For Comments”; basically, they’re specifications for the protocols):
FTP:
ftp://ftp.isi.edu/in-notes/rfc959.txt
HTTP:
ftp://ftp.isi.edu/in-notes/rfc2616.txt
Along the same lines, there’s also
SMTP - Simple Mail Transfer Protocol - the protocol over which email is sent over the internet
NNTP - Network News Transfer Protocol - ibid, but for Usenet.
Don’t forget POP - Post Office Protocol - the protocol with which e-mail is received over the Internet.
This first question has been adequately addressed. (Did you just search on the web for “http”? Just kidding.)
Because they said so. You’re asking about the syntax of Internet URLs (Uniform Resource Locators), which is a way of specifying resources on the Internet as a string of characters. The specification is in RFC 1738.
I’ll summarize. The syntax of a URL is:
<scheme>:<scheme-specific-part>
That is, a URL consists of two parts, the and the , separated by a colon. The schemes are things like “http”, “ftp”, “mailto”, and my favorite “prospero”. The colon is there just to separate the scheme from the rest. It’s just a separator.
The syntax of the scheme specific part depends on the scheme. The scheme specific data for most schemes starts with two slashes, “mailto” and “news” are notable exceptions. For http URLs, the scheme specific part is:
//<host>:<port>/<path>?<searchpart>
The host is an Internet host, either an IP address (four numbers between 0 and 255 inclusive, separated by dots) or the fully qualified domain name of the host. The port number is between 0 and 65535; for http it defaults to port 80, and can be ommitted (along with the colon that precedes the port).
So, the colon is there to separate the scheme from the scheme-specific-part; and the two slashes are there to mark the beginning of the scheme-specific-part. A little redundant? Sure, but the gremlins in the internet and the leprechauns inside your computer like it that way.
(kgmm)/(s*s)