French web developer mainly but touches everything. Volunteer admin mod here at DEV. I learn AI and Astro at this moment and databases. — Addict to Cappuccino and Music
GET is just a method. How it is implemented on the server is up to the server.
You could run all your API on GET and act upon either the URL components or the body of the GET (there should be none, but you can use one).
GET /list → lists your objects GET /name/add/john → adds the name "john" GET /name/delete/john → deletes "john"
Sure, the nice way is to use PUT, DELETE etc. but the above can work perfectly. This is actually used by some APIs.
Of course, according to the specification, GET is expected to be idempotent but, again, this is just an expectation, the server can do whatever pleases it.
Right, I misunderstood you, thanks for clarifying your point!
The article assumes a correct implementation of GET which follows from the specification. I will add an edit to state that explicitly.
My 35+ year career includes process analysis and design, managing projects, and implementing systems for corporate, government, and non-profit organizations.
Location
Little Rock, Arkansas
Education
UA Little Rock - Finance & MIS | Cornell - Corp. Finance | Stanford - Project Management
Work
Business Analyst | Product Manager | Project Manager at BitByByte Solutions
Really detailed post on where it matters. Very well done, congrats!
Okaaaay, this is a big and a great post ! Good job!
Awesomz explanation 🙏👏👏👏
Very nice article.
GET is idempotent only if the server says so. There is nothing in the protocol itself they would enforce it.
Thank you!!
I have to disagree, however. I believe that, according to datatracker.ietf.org/doc/html/rfc7..., GET is in fact both a safe and idempotent method!
GETis just a method. How it is implemented on the server is up to the server.You could run all your API on
GETand act upon either the URL components or the body of theGET(there should be none, but you can use one).GET /list→ lists your objectsGET /name/add/john→ adds the name "john"GET /name/delete/john→ deletes "john"Sure, the nice way is to use
PUT,DELETEetc. but the above can work perfectly. This is actually used by some APIs.Of course, according to the specification,
GETis expected to be idempotent but, again, this is just an expectation, the server can do whatever pleases it.Right, I misunderstood you, thanks for clarifying your point!
The article assumes a correct implementation of
GETwhich follows from the specification. I will add an edit to state that explicitly.One of the most fleshy and, at the same time, concise articles I've ever read about this not-so-easy field.
Thanks so much for your share!
Thanks, I learned a lot of details of the whole proccess from this article.
Awsome work dude 👍
very intuitive, finally got to know what happens under the hood for a website loading
Really great work!! 🦄
Thank you, Paulo, for creating and sharing this fabulous tutorial.
_great post brother really love the way you describes the browser working structure
love from India _
This was deep ! like I think pacific trench just smiled after reading this:)
Thanks!