3 ms·
This seems like an... unnecessarily angry... bit of a rant. BUT, I tend to agree. Just use GET for all requests that don't change things, and POST for those th
by crazygringo 8y ago
This seems like an... unnecessarily angry... bit of a rant.
BUT, I tend to agree. Just use GET for all requests that don't change things, and POST for those that do (important so spiders and pre-caching don't inadvertently take actions), and put everything else (including what the real verb is) in the URL or parameters.
The idea of trying to shoehorn your logic into additional PUT and DELETE verbs is unnecessary and makes it harder to use/support (e.g. HTTP forms don't support those verbs).
And... that's it. Fortunately I've never had to work with a die-hard REST evangelist, so maybe I've never had to feel the anger or frustration this post must be coming from...