Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

IDEMPOTENT and NON-IDEMPOTENT

 
Hendy Setyo Mulyo
Ranch Hand
Posts: 219
Firefox Browser Java Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi ranchers,

According to SCWCDHints by Jothi,

1) Of the big 7 HTTP methods,
SAFE >> GET, HEAD, TRACE, OPTIONS
IDEMPOTENT >> GET, HEAD, TRACE, OPTIONS, PUT, DELETE
NON-IDEMPOTENT >> POST

I know that GET HEAD TRACE and OPTIONS are obviously SAFE and IDEMPOTENT.
But why PUT and DELETE are also IDEMPOTENT? I thought they will make changes on the server hence should be NON-IDEMPOTENT as well as POST?
 
Marc Peabody
pie sneak
Sheriff
Posts: 4727
Mac Ruby VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From Wikipedia:
Methods GET, HEAD, PUT and DELETE are defined to be idempotent, meaning that multiple identical requests should have the same effect as a single request. Methods OPTIONS and TRACE, being safe, are inherently idempotent.
 
Joe Harry
Ranch Hand
Posts: 10128
3
Eclipse IDE Mac PPC Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Refer http://faq.javaranch.com/view?ScwcdHints
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic