Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 2
    From What I know, POST is not idempotent.en.wikipedia.org/wiki/POST_(HTTP)#Affecting_server_state Commented Jan 23, 2013 at 8:34
  • @Mithir: POST is not assumed to be idempotent; it still can be. But it's true that since all REST operations are supposed to be idempotent, POST has basically no place in REST. Commented Jan 23, 2013 at 8:46
  • 1
    I'm confused... content I've read and existing implementation I'm familiar with(ServiceStack, ASP.NET Web API), all suggests that POST has a place in REST. Commented Jan 23, 2013 at 9:01
  • 3
    In REST idempotence is assigned to the resource, not the protocol or its response codes. Thus, in REST over HTTP the methods GET, PUT, DELETE, PATCH and so on are considered idempotent although their response codes may vary for subsequent calls. POST is idempotent in the sense that every call creates a new resource. See Fielding's It is OK to use POST. Commented Jan 23, 2013 at 14:47
  • 2
    Operations that are not idempotent are allowed in rest. That assertion is flat out wrong. Commented Oct 22, 2015 at 1:34