Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

PUT vs POST More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Idempotence (Score:1)

by jordan (120) on 2006.06.16 13:11 (#48237) Homepage Journal

I think the most important distinction to remember between PUT vs. POST is that PUT is intended to be idempotent and POST is not.

You should be able to PUT the same resource with the same data and it have no additional effect, after the first time.

Remember also that the agent (client) submitting a PUT request should be able to tell if this is a new resource being created through the 201 response, although in practice this is heavily abused and many programs always return 200 responses for all success.

Reply to This
- Re:Idempotence (Score:2)
  
  by lachoy (1663)
  
  Yep, I forgot to mention this. An interesting thing about the idempotence discussion is that people confuse "I submit foo once or twenty times and get the same response" versus "I will have no side effects on the server from submitting foo."

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.