6 ms·
Use GET for everything that can be cached and repeated without side-effects, and POST for everything else. You can delete the rest of the spec and clients can
by egeozcan 5y ago
Use GET for everything that can be cached and repeated without side-effects, and POST for everything else.
You can delete the rest of the spec and clients can connect without head-aches but only if you can put up with the fanatics in your team trying to trace every bug to not following rest, in the rare case giving you no options other than trying patch after patch to make everything rest-compliant.
- hakre 5y ago> Use GET for everything that can be cached and repeated without side-effects As long as HTTP is concerned (which must not be specifically REST), HEAD needs to be supported next to GET, too.
- nojs 5y ago> Use GET for everything that can be cached and repeated without side-effects *except when the query string is too big, then use POST