http:// means something after all
Identify the components of a URL
View requests and responses in the browser
Make requests using something other than a browser
Identify the components of a request and response in HyperText Transfer Protocol
But like, for reals how does it work
First implementation of TCP
First implementation of DNS
First computer system secure enough to share classified documents across a network
IP
TCP / UDP
Data Link (OS-level stuff)
HTTP
The Browser
IP
TCP / UDP
Data Link (OS-level stuff)
HTTP
The Browser
Literally cables and wifi
IP
TCP / UDP
Data Link
HTTP
The Server
IP
TCP / UDP
Data Link (OS-level stuff)
HTTP
The Browser
When someone says "Packets", think TCP / UDP layer
Requests
Responses
Identify a resource via it's uniform resource identifier
Input the identifier into a client
Direct the client to make a request
Uniform Resource Identifiers
Browsers aren't the only thing that can make requests
Uniform Resource Identifiers
URLs are URIs
Uniform Resource Identifiers
URLs are URIs
http://galvanize.com/blog/
IP
TCP / UDP
Data Link (OS-level stuff)
HTTP
The Browser
IP
TCP / UDP
Data Link (OS-level stuff)
HTTP
The Browser
IP
TCP / UDP
Data Link (OS-level stuff)
HTTP
The Browser
$ traceroute galvanize.com
Packets Contain a "TTL" header
Packets Contain a "TTL" header
TTL : Time to Live
Packets Contain a "TTL" header
TTL : Time to Live
Really means "don't visit more than x places when you're looking for a way to your destination"