GET vs. POST Revisited

By Deane Barker on October 30, 2006

POST Considered Inconvenient: Another solid rant on GET vs. POST. The author makes the argument that you should always use GET, unless the script “is not safe,” in which case you should use POST.

This dual method approach is a common antipattern in web apps. You should never have the same script that blithely accepts the same parameters via GET or POST and returns the same value. The script should pick one and stick to it. If the script is safe, then use GET. If the script is unsafe (i.e. has side effects) use POST. However it is not appropriate to pick both. That either loses search engine juice and linkability (using POST where GET is called for) or opens security holes (using GET where POST is called for).

The argument for GET:

POST requests cannot be bookmarked, linked to, indexed, searched, or cached. […] GET is vastly friendlier to users and dramatically improves your search engine placement.



  1. I agree that when it comes to a search and results situation, or some sort of navigation, using the GET method is easier and friendlier for the end user. However, do you really want to upload a 10MB binary file using GET? Insert critical information into a database using GET? As with everything, both GET and POST have their strengths and weaknesses, but to say that you should ALWAYS use GET (even when a user-friendly URL is not needed) is overzealous in my book.

Comments are closed. If you have something you really want to say, tweet @gadgetopia.