Comments on: POST vs. PUT

By: HTTP Request/Response Basics | DEVHUB.FM

HTTP Request/Response Basics | DEVHUB.FM — Sat, 04 Feb 2012 23:23:00 +0000

[...] reading: HTTP 1.1 specification PUT vs. POST HTTP TRACE Vulnerability Blog Post Restful HTTP PUT/POST Article HTTP CONNECT Security White Paper [...]

By: HTTP Request/Response Introduction | DEVHUB.FM

HTTP Request/Response Introduction | DEVHUB.FM — Sat, 04 Feb 2012 23:16:03 +0000

[...] reading: HTTP 1.1 specification PUT vs. POST HTTP TRACE Vulnerability Blog Post Restful HTTP PUT/POST Article HTTP CONNECT Security White Paper [...]

By: Mark

Mark — Thu, 16 Jun 2011 05:10:11 +0000

Great summary. One question…. if one POSTs and the resource already exists, what is an appropriate response code?? If we wanted to replace the resource we would PUT but in this scenario its not the case.

By: PUT or POST: The REST of the Story | ss's space

PUT or POST: The REST of the Story | ss's space — Fri, 08 Apr 2011 03:28:30 +0000

[...] POST vs. PUT [...]

By: Faking PUT, etc. over POST : 9877

Faking PUT, etc. over POST : 9877 — Tue, 13 Apr 2010 21:12:18 +0000

[...] to let my resources handle @PUTs for updates where a URI is known ahead of time in keeping with http://www.elharo.com/blog/software-development/web-development/2005/12/08/post-vs-put/, among [...]

By: Dennis

Dennis — Tue, 23 Mar 2010 16:58:01 +0000

Well I have a friend who uses PUT to upload highscores from an Android phone. It’s a Sudoku application.

When I told him he should use post and keep put at Webdav and uploading pages he said it’s up to the server what to do with it. Of course, that’s true.
But still it’s like using any IP other than 192.168, 10, 172.16-33 in a private network. It will work (until you want to access a real server with that ip, of course) but it’s wrong.

Could it be possible that some networks’ http proxy servers block the incoming put requests or just throw them away?

By: Amit Mittal

Amit Mittal — Fri, 19 Mar 2010 14:10:42 +0000

Spot ON!!!

Thanks a lot. Finally I have clearly understood the difference. Most of the explanations I found prior to this focused on ‘Insert’ and ‘Update’ approach to this which I didn’t find convincing enough.

This one is really awesome.

By: Mark

Mark — Tue, 26 Jan 2010 12:37:30 +0000

If you have to use the analogy:

PUT = REPLACE (http://dev.mysql.com/doc/refman/5.0/en/replace.html)

POST = CALL (stored procedures)

By: PUT or POST: The REST of the Story « Open Sourcery

PUT or POST: The REST of the Story « Open Sourcery — Thu, 16 Oct 2008 22:51:23 +0000

[...] POST vs. PUT [...]

By: Elliotte Rusty Harold

Elliotte Rusty Harold — Mon, 13 Oct 2008 13:14:43 +0000

Your understanding of HTTP is understandable but incorrect. AtomPub is correct.

PUT is update or create with a user-supplied URL. POST is create with a server generated URL. There are no custom actions at all. That is one of the key principles of REST. Resolving an incident, reopeningt a ticket, etc. are all defined as one of four actions (PUT, POST, GET, DELETE) on a resource. For instance to reopen a ticket, you might PUT the text “true” to http://www.example.com/tickets/42389349/opened.