<ol>
<li>GET ⭐️</li>
<li>POST ⭐️</li>
<li>PUT ⭐️</li>
<li>PATCH</li>
<li>DELETE ⭐️</li>
<li>HEAD</li>
<li>OPTIONS ⭐️</li>
<li>TRACE</li>
<li>CONNECT</li>
</ol>
👍🏿 Subscribe to our newsletter - <a href="https://bit.ly/3x4j5dT" target="_blank" rel="noopener nofollow">https://bit.ly/3x4j5dT</a>
<img src="https://media.daily.dev/image/upload/s--_WIRNsFn--/f_auto/v1723727363/ugc/content_b29186e1-461e-4bbb-82b0-097a4ca270c2" alt="http request METHODS">
#systemdesign #coding #interviewtips

Dive into the freshest insights, best practices, and bleeding-edge trends in Backend and DevOps Engineering.

Amigoscode

The post lists nine essential HTTP methods that developers should know, including GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, and CONNECT. Each method is crucial for different actions in web development and API interactions.

9 HTTP Methods that you MUST KNOW

A typo mistake POST is used to send “data” to server to create a new resource. It doesn’t return all customers but the status of request and any relevant info of created resource.
This article is short and easy to rewind for interview purpose and for general info for developers.

This is a terrible cheatsheet. Most of what it says is useless and has nothing to do with the actual Request METHOD.
GET -&gt; sends a GET request to the server asking for it to send something back. It could be anything, your urls, your images, css, js, pdfs, etc all get loaded via GET requests. It has nothing to do with customers except the example is what a customers api endpoint MIGHT look like. GET requests are used to pass parameters in the url itself like /bob?jim=1
POST -&gt; Also requests information from the server but is used to send parameters in the POST payload object instead of in the url.
The description on it doesn’t even match the customer url above it…ridiculous. POST is generally meant to be used to CREATE a new object on the server.
PUT -&gt; is meant to send a request to the server that says “Edit some object”.
PATCH -&gt; is also meant to edit some object but not the whole object
DELETE -&gt; is meant to send deletion requests, but just using DELETE won’t do jack your server has to be configured to process it to actually apply the deletion
HEAD -&gt; this one is the “different” one in that it returns only the headers of the response and not the body. So you can make requests to see the status of a url without getting a full response back.
OPTIONS -&gt; you all love this one, it’s used for cross site requests and is what’s used when you get your CORS errors. You need to always allow it if you want external urls to send requests to yours.
TRACE -&gt; is only used to test and debug to see what steps a request goes through to get to the server and back to you.
CONNECT -&gt; creates a browser connection to that url and is not something you normally use in your code.
Technically, the first 5 [GET, POST, PUT, PATCH, DELETE] can all be done via POST [which is more secure than GET and easier to lock down] since for all of them you have to configure your server code to make the actual step. So you see tons of systems that do something like POST ?action=update or action=delete in order to tell the server which action to perform.
Only purists insist on using all these “proper request methods”…but frankly your users don’t care and using just one means you have less attack surface and less to configure.
Holy crap that cheatsheet sucks.

Wow, I had never heard of HEAD, OPTIONS or TRACE! Thanks for sharing! Love infogrphics like these, makes learning much easier.

what is the difference between PUT and PATCH ?

Thanks for sharing will learn more about it 😊 and try to use them in my code 🥳