The Internet’s Universal Verbs
At its core, the internet is a massive, ongoing conversation between your device (the client) and a website's server. To keep this chat from becoming chaos, they follow a set of rules called the Hypertext Transfer Protocol, or HTTP. Think of HTTP as the grammar
for this conversation. And if HTTP is the grammar, then HTTP methods are the verbs. They are the specific actions your browser can ask a server to perform. Without these standardized commands, every interaction would be a guessing game. Instead, we have a small, reliable toolkit of verbs that powers almost every piece of software you use, from mobile apps to the browser you're reading this on.
GET: Just Looking, Thanks
The most common method by far is GET. A GET request is the simplest action: you’re just asking for information. It’s the equivalent of walking into a library and asking the librarian for a book. You aren’t changing the library's collection; you are just retrieving something that's already there. When you type a website into your address bar and hit Enter, your browser sends a GET request to that site's server, which then returns the webpage. When you scroll through Instagram, your app is sending a stream of GET requests to fetch the next batch of photos. Because GET requests are “read-only,” they are considered a “safe” method, meaning they don't alter anything on the server.
POST: Sending a Package of Information
If GET is for reading, POST is for writing. A POST request is used to send data to the server, often to create a new resource. Think of it like filling out a form and handing it over a counter. When you log into an account, type a comment on a video, or complete a checkout process, you’re using a POST request. Your browser bundles up the information you entered—your username, password, or credit card details—and sends it to the server. Unlike a GET request, a POST request changes the state of the server; it adds your comment, creates your user session, or places your order. This is the workhorse method for making the web interactive.
The Supporting Cast: PUT and DELETE
While GET and POST handle most of the traffic, a few other methods play crucial supporting roles. The PUT method is used to update an existing resource. If you go to your profile page and change your bio, you might be sending a PUT request that replaces your old bio with the new one. It's like replacing a file in a filing cabinet with a completely new version. On the other hand, the DELETE method does exactly what it sounds like: it tells the server to remove a resource. When you delete a tweet or remove an item from your online shopping cart, you're sending a DELETE request. Together, these methods provide a full suite of actions: create (POST), read (GET), update (PUT), and delete (DELETE), often referred to by the acronym CRUD.
Bringing It All Together
Imagine you're ordering a pizza online. First, you send a GET request to load the restaurant's menu page. You then fill out your order and press the 'submit' button, which sends a POST request to the server containing your pizza choices and address. The server creates your order in its system. Ten minutes later, you realize you forgot to add extra cheese. You go to your order history (a GET request), click 'edit order,' and add the cheese. This could trigger a PUT request to update your existing order with the new information. These simple, predictable commands, working silently in the background, are what make the complex dance of modern software possible, turning your clicks into concrete actions.
