Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



> 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.


> Use GET for everything that can be cached and repeated without side-effects

*except when the query string is too big, then use POST




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: