W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1999

WebDAV methods: safe and idempotent

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Mon, 26 Jul 1999 21:15:42 -0700
To: WebDAV WG <w3c-dist-auth@w3.org>
Message-ID: <NDBBIKLAGLCOPGKGADOJGECDCCAA.ejw@ics.uci.edu>
Off-list, I was asked about the "idempotence" and "safety" of WebDAV
methods, following the definitions of "safe" and "idempotent" provided in
Section 9.1 ("Safe and Idempotent Methods") of RFC 2616. (Basically, "safe"
= does not harm the state of the resource, "idempotent" = the effect of N >
0 identical requests is the same as a single request)  In HTTP/1.1, GET,
HEAD, OPTIONS, and TRACE are safe (the rest are not), while GET, HEAD, PUT,
DELETE, OPTIONS, and TRACE are idempotent.  For the record:

PROPFIND: safe, idempotent
PROPPATCH: unsafe, idempotent
MOVE: unsafe, non-idempotent
COPY: unsafe, idempotent
MKCOL: unsafe, idempotent
LOCK: safe, non-idempotent
UNLOCK: safe, non-idempotent

New method specifications should indicate their idempotence and safety.

In advanced collections:

MKREF: unsafe, idempotent
BIND: unsafe, idempotent
ORDERPATCH: unsafe, non-idempotent (in general, though some ORDERPATCH
requests might be idempotent)

- Jim
Received on Tuesday, 27 July 1999 00:19:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:51 GMT