Last time we learned about clients and servers. Now let's dive deeper into what happens when the client (your browser) actually "places an order."
When you visit a website, your browser creates an HTTP request. This is a formatted message sent to the server.
Engagement Message
Name one thing your browser includes in this request.
An HTTP request is like a detailed restaurant order. It tells the server exactly what you want and how you want it.
Just like you might say, "I want a burger, medium rare, no onions," your browser gives the server specific instructions.
Engagement Message
Give one example of an instruction a browser might send to a server.
The most important part of any HTTP request is the method. This tells the server what action you want to perform.
Think of it like different types of requests you might make at a restaurant: ordering food, asking for the check, or requesting a refund.
Engagement Message
What's one action you might want to perform on a website?
The most common HTTP method is GET. When you use GET, you're asking the server to "get" or retrieve something—like a webpage, an image, or some data.
It's like asking your waiter, "Can I see the menu?" You're not changing anything, just requesting information.
Engagement Message
When would your browser typically send a GET request?
Another important method is POST. This is used when you want to send, or "post," new information to the server.
It's like placing your actual food order—you're giving the restaurant new information (your order) that they need to process.
Engagement Message
Name one example of information you might POST to a website.
