I screen candidates for this freelancing company part time and i meet all kinds of people. I asked a self proclaimed senior engineer the difference between a get and a post request and he told me with the utmost confidence. “they are both the same”. That’s it. No other explanation was offered.
We were both just stared through the screen awkwardly.

wtf

But aren't they?

That’s sad....

Haha. Should’ve asked him about PATCH.
And be cursed people using “PATCH” in their APIs !

@A4Abhiraj they are not. In a standard restful api design, each has its own purpose.

@NoToJavaScript What's wrong with PATCH?

For anyone wondering what the difference is, a GET request is a request to receive data and a POST request contains data to be received.

Example: your browser GETs a webpage and then POSTs your login details back to the server to let you login.

@homo-lorens

It’s very difficult to implement in a strongly typed languages. AND requires some manual coding. For Example in C# you get out of box GetAsync and PostAsync (And some others), but not “patch”.
And honestly, the only reason I see for using patch is to reduce the traffic. I prefer just PUT the whole object and be done with it. 1 line of code.
Patch will require to properly manage serialization and being attentive to details (Who has the time for that ?)

@pythontrader

Yes, but you hit the limit of Get pretty fast with complex filters etc.
I see no problems for using POST for getting data if request object is complex

@witchDev it.was.a.joke.

@NoToJavaScript I use PATCH as an alternative to POST when representing "edit" actions. PUT is completely different as it is required to be idempotent, and therefore poses strict limitations on the API design. C# not supporting PatchAsync is incredibly stupid, it's literally the exact same as POST just with a different verb. There are 5 HTTP verbs and all tools I know understand all of them.