URL
(Human readable addressing)
But we really want to go to 36.16085, -86.773903...
by car...
and to the second floor...
room 202.
HyperText Transfer Protocol - Secure
Other protocols you might know...
FTP,
POP,
SMTP,
SSL,
DHCP,
TCP,
SSH
subdomain.SLD.TLD
Common TLD's: .com, .org, .gov
Examples of SLD's: google, whitehouse, facebook
Typical subdomains: www, mail, blog
This is not a real directory structure!
http://www.beggsandpartners.com/plumbing-heating/overview/
We just typed in:
http://www.google.com/search/howsearchworks/
But where do we really want to go?
The first machine to know the answer wins!
The first machine to know the answer wins!
The first machine to know the answer wins!
The first machine to know the answer wins!
The first machine to know the answer wins!
The first machine to know the answer wins!
Now we know where to go to get content from Google:
74.125.227.36
But what is that number?
It's an IP - address.
A machine-readable identifier for a network interface
(not for the whole machine!)
Set of four numbers,
between 0 and 255
(that's 8 bits each, making a 32-bit address)
74. | 125.227.26 |
Network ID (1-126, Class A) | Host (interface) ID |
Your computer at home has an IP address, too!
But why does it always start with 192?
It's a private network,
and every device you have has a private IP!
Why the need for a new version of IP addressing?
Seems to work just fine...
We started running out of IPv4 addresses in 2011.
Imagine a monitor with 105px per inch,
and 1px per IP address...
http://pthree.org/2009/03/08/the-sheer-size-of-ipv6/
GET /search/howsearchworks/ HTTP/1.1
Host: www.google.com
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Connection: keep-alive
Cookie: 1%2FcA8CoqFFr9udmhMd2NpbtBcfH9Rzdd9fE5ISkdmB%2F...
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...
...
There is usually a LOT more in a REQUEST, this is just a sample of some potential data.
GET /search/howsearchworks/ HTTP/1.1
Cookie: 1%2FcA8CoqFFr9udmhMd2NpbtBcfH9Rzdd9fE5ISkdmB%2F2023-05-09+15%3A21%3A59
Cookie: 1/cA8CoqFFr9udmhMd2NpbtBcfH9Rzdd9fE5ISkdmB/2023-05-09 15:21:59
HTTP/1.1 200 OK
Date: Mon, 28 Mar 2016 09:15:00 GMT
Server: Apache/1.3.3.7 (Unix) (Red-Hat/Linux)
Last-Modified: Mon, 08 Jan 2016 23:11:55 GMT
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Content-Type: text/html; charset=UTF-8
Content-Length: 220
Expires: Fri, 01 Jan 2020 00:00:00 GMT
X-Search-Version: 245.136
<!DOCTYPE html><html><head>...</head><body>...</body></html>
As with the REQUEST data, there can - and usually is - much more data in the RESPONSE, this is just a brief sampling.
HTTP/1.1 200 OK
<!DOCTYPE html><html><head>...</head><body>...</body></html>
DOCTYPE
<head>
element<meta>
tags (in order)<link>
& <script>
tagsdefer
ed)<body>
element<body>
(<img>
, <script>
, <video>
, etc)<head>
to <body>
SSL (TLS)- encrypt data sent to and from a client/server
A Certificate Authority (CA) guarantees
the holder of the certificate is who they say they are.
They are the gatekeepers.
Examples of ROOT CA's: Verisign, Thawte, GeoTrust, etc.
Certificates from root CA's can cost over $3,000
But I hear you can get one for free...
http://datacenteroverlords.com/2011/09/25/ssl-who-do-you-trust/
http://datacenteroverlords.com/2011/09/25/ssl-who-do-you-trust/
http://datacenteroverlords.com/2011/09/25/ssl-who-do-you-trust/