Examples
a. Example 1
b. Example 2
Exercise!
What We're Covering
Examples
a. Example 1
b. Example 2
Exercise!
What We're Covering
Examples
a. Example 1
b. Example 2
Exercise!
How does google return your search results to your device?
How does a web page just appear on your device?
How do your mom/kids see what you do on facebook?
When you login to Instagram how do they know it's you?
How do you think your devices talk to Google, Facebook, and websites in general?
What We're Covering
Examples
a. Example 1
b. Example 2
Exercise!
Speaking and communication shouldn't be taught from me.
Though there are a lot of parallels between how computers talk and how we talk.
Air between us
The magic of speech and conversation happens here!
Request or gives info
Air between us
Response to request
Air between us
Requests to give or ask for information.
Responds to the request from the client.
What We're Covering
HTTP is like communication, let's communicate!
Examples
a. Example 1
b. Example 2
Exercise!
This person is the client.
Request or gives info
The internet
(Client)
This person would be the server in this scenario.
Response to request
Air between us
(Server)
What We're Covering
HTTP is like communication, let's communicate!
Difference between the client (requester) and server (responder)
Examples
a. Example 1
b. Example 2
Exercise!
You can request (and give) information a few different ways.
Please note that this is done on the client side.
Asking for information from the server.
people: asking a question
computers: asking for google.com
Giving information to a server, new or existing.
people: Telling other people that you have animals.
computers: logging in, posting on a platform
A few other methods are (We're not going to go into these in depth)
Updating already existing information on the server.
people: giving more information about an existing thing
ie. giving people your phone number
computers: updating existing information to a user
Deleting Information
people: forget about this!
computers: remove this information now!
What We're Covering
HTTP is like communication, let's communicate!
Difference between the client (requester) and server (responder)
Examples
a. Example 1
b. Example 2
Exercise!
Everything is okay! The Server has fulfilled the request (any type)
This is the request you want to see the most.
Sending this request somewhere else. The Server is redirecting the response to a more appropriate place where it can be fulfilled.
Server can't find what you're looking for (Client's error).
For Example a blog post that can't be found.
This request could also tell a client that it doesn't have permission to do the action its' trying to do on the server.
Server error, For example if there's a weird syntax error on the server (computer). Also this would be like if someone is asking something that you know about but is asking it to you in Greek.
What We're Covering
Examples
a. Example 1
b. Example 2
Exercise!
Do you have cats?
1. Ask if I have cats.
Air between us
2. I'll respond to tell you that I do have cats
I have three cute cats
Air between us
Server
This will be sent with a token to show that we can trust the client (I'll cover that later).
The Internet
Client
Server
Client
Status 200
You can see the website!
If the token is correct, we'll give the information.
The Internet
What We're Covering
Talk about how HTTP is like talking
Examples
a. Example 1
b. Example 2
Exercise!
My dog is named Spot
1. Tell me you have dog named Spot
Air between us
Me
You
2. I'll respond to tell you that I understand that you have a dog named spot
Thanks! I bet he's cute!
Note:
I'll only remember if I trust this person, otherwise I'll throw this information away.
Air between us
Server
POST dog picture to twitter
Text
The Internet
Client
Server
Status 204
The server responds with your post being successful.
The Internet
Client
What We're Covering
Talk about how HTTP is like talking
Examples
a. Example 1
b. Example 2
Exercise!
1. Pair up!
2. One of you will be the server and the other will be the client.
3. Given act out your scenario decide the following:
a. Which is the request, Which is the response?
b. what kind of HTTP request is the client using?
c. What kind of response did the server use?
End of the lesson participants should be able to identify HTTP requests.
We've identified the different HTTP request and response types, and hopefully we understand them a bit better.
Marshmallow
Ghost
Gambit