Note: a later version of this document has been published as RFC 7237.
This document registers those Hypertext Transfer Protocol (HTTP) methods that have been defined in RFCs before the IANA HTTP Method Registry was established.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.
This Internet-Draft will expire in December 2014.
Copyright © 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Discussion of this draft takes place on the HTTPBIS working group mailing list (email@example.com), which is archived at <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
The current issues list is at <http://trac.tools.ietf.org/wg/httpbis/trac/query?component=method-registrations> and related documents (including fancy diffs) can be found at <http://tools.ietf.org/wg/httpbis/>.
This is a temporary document for the purpose of tracking the editorial changes made during the AUTH48 (RFC publication) phase.
There are no security considerations related to the registration itself.¶
Security considerations applicable to the individual HTTP methods ought to be discussed in the specifications that define them.¶
The table below provides registrations of HTTP method names that have been added to the IANA "Hypertext Transfer Protocol (HTTP) Method Registry" at <http://www.iana.org/assignments/http-methods> (see Section 8.1 of [RFC7231]).¶
|ACL||no||yes||[RFC3744], Section 8.1|
|BASELINE-CONTROL||no||yes||[RFC3253], Section 12.6|
|BIND||no||yes||[RFC5842], Section 4|
|CHECKIN||no||yes||[RFC3253], Section 4.4 and [RFC3253], Section 9.4|
|CHECKOUT||no||yes||[RFC3253], Section 4.3 and [RFC3253], Section 8.8|
|COPY||no||yes||[RFC4918], Section 9.8|
|LABEL||no||yes||[RFC3253], Section 8.2|
|LINK||no||yes||[RFC2068], Section 18.104.22.168|
|LOCK||no||no||[RFC4918], Section 9.10|
|MERGE||no||yes||[RFC3253], Section 11.2|
|MKACTIVITY||no||yes||[RFC3253], Section 13.5|
|MKCALENDAR||no||yes||[RFC4791], Section 5.3.1|
|MKCOL||no||yes||[RFC4918], Section 9.3|
|MKREDIRECTREF||no||yes||[RFC4437], Section 6|
|MKWORKSPACE||no||yes||[RFC3253], Section 6.3|
|MOVE||no||yes||[RFC4918], Section 9.9|
|ORDERPATCH||no||yes||[RFC3648], Section 7|
|PATCH||no||no||[RFC5789], Section 2|
|PROPFIND||yes||yes||[RFC4918], Section 9.1|
|PROPPATCH||no||yes||[RFC4918], Section 9.2|
|REBIND||no||yes||[RFC5842], Section 6|
|REPORT||yes||yes||[RFC3253], Section 3.6|
|SEARCH||yes||yes||[RFC5323], Section 2|
|UNBIND||no||yes||[RFC5842], Section 5|
|UNCHECKOUT||no||yes||[RFC3253], Section 4.5|
|UNLINK||no||yes||[RFC2068], Section 22.214.171.124|
|UNLOCK||no||yes||[RFC4918], Section 9.11|
|UPDATE||no||yes||[RFC3253], Section 7.1|
|UPDATEREDIRECTREF||no||yes||[RFC4437], Section 7|
|VERSION-CONTROL||no||yes||[RFC3253], Section 3.5|