|Network Working Group||J. Reschke|
|Updates: 2616, 2817 (if approved)||July 2007|
|Intended status: Best Current Practice|
|Expires: January 2008|
By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.
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”.
The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
This Internet-Draft will expire in January 2008.
Copyright © The IETF Trust (2007). All Rights Reserved.
The Hypertext Transfer Protocol (HTTP) Status Code Registry defines the name space for the Status-Code token in the Status line of an HTTP response (see RFC2616).
Previously, both the registration procedure and the initial registry contents were defined by RFC2817. This specification moves this aspect of RFC2817 into a separate standards-track document for easier maintenance.
Distribution of this document is unlimited. Please send comments to the Hypertext Transfer Protocol (HTTP) mailing list at email@example.com, which may be joined by sending a message with subject "subscribe" to firstname.lastname@example.org.
Discussions of the HTTP working group are archived at <http://lists.w3.org/Archives/Public/ietf-http-wg/>.
XML versions, latest edits and the issues list for this document are available from <http://greenbytes.de/tech/webdav/#draft-reschke-http-status-registry>.
Values to be added to this name space SHOULD be subject to review in the form of a standards track document within the IETF Applications Area. Any such document SHOULD be traceable through statuses of either 'Obsoletes' or 'Updates' to this document.¶
No security considerations are introduced by this document beyond those already inherent in use of the referenced HTTP status codes.¶
|[RFC2295]||Holtman, K. and A. Mutz, “Transparent Content Negotiation in HTTP”, RFC 2295, March 1998.|
|[RFC2518]||Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D. Jensen, “HTTP Extensions for Distributed Authoring -- WEBDAV”, RFC 2518, February 1999.|
|[RFC2616]||Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L., Leach, P., and T. Berners-Lee, “Hypertext Transfer Protocol -- HTTP/1.1”, RFC 2616, June 1999.|
|[RFC2774]||Nielsen, H., Leach, P., and S. Lawrence, “An HTTP Extension Framework”, RFC 2774, February 2000.|
|[RFC2817]||Khare, R. and S. Lawrence, “Upgrading to TLS Within HTTP/1.1”, RFC 2817, May 2000.|
|[RFC3229]||Mogul, J., Krishnamurthy, B., Douglis, F., Feldmann, A., Goland, Y., van Hoff, A., and D. Hellerstein, “Delta encoding in HTTP”, RFC 3229, January 2002.|
|[RFC4918]||Dusseault, L., Ed., “HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)”, RFC 4918, June 2007.|
|100||Continue||[RFC2616], Section 10.1.1|
|101||Switching Protocols||[RFC2616], Section 10.1.2|
|102||Processing||[RFC2518], Section 10.1|
|200||OK||[RFC2616], Section 10.2.1|
|201||Created||[RFC2616], Section 10.2.2|
|202||Accepted||[RFC2616], Section 10.2.3|
|203||Non-Authoritative Information||[RFC2616], Section 10.2.4|
|204||No Content||[RFC2616], Section 10.2.5|
|205||Reset Content||[RFC2616], Section 10.2.6|
|206||Partial Content||[RFC2616], Section 10.2.7|
|207||Multi-Status||[RFC4918], Section 11.1|
|226||IM Used||[RFC3229], Section 10.4.1|
|300||Multiple Choices||[RFC2616], Section 10.3.1|
|301||Moved Permanently||[RFC2616], Section 10.3.2|
|302||Found||[RFC2616], Section 10.3.3|
|303||See Other||[RFC2616], Section 10.3.4|
|304||Not Modified||[RFC2616], Section 10.3.5|
|305||Use Proxy||[RFC2616], Section 10.3.6|
|306||(Reserved)||[RFC2616], Section 10.3.7|
|307||Temporary Redirect||[RFC2616], Section 10.3.8|
|400||Bad Request||[RFC2616], Section 10.4.1|
|401||Unauthorized||[RFC2616], Section 10.4.2|
|402||Payment Required||[RFC2616], Section 10.4.3|
|403||Forbidden||[RFC2616], Section 10.4.4|
|404||Not Found||[RFC2616], Section 10.4.5|
|405||Method Not Allowed||[RFC2616], Section 10.4.6|
|406||Not Acceptable||[RFC2616], Section 10.4.7|
|407||Proxy Authentication Required||[RFC2616], Section 10.4.8|
|408||Request Timeout||[RFC2616], Section 10.4.9|
|409||Conflict||[RFC2616], Section 10.4.10|
|410||Gone||[RFC2616], Section 10.4.11|
|411||Length Required||[RFC2616], Section 10.4.12|
|412||Precondition Failed||[RFC2616], Section 10.4.13|
|413||Request Entity Too Large||[RFC2616], Section 10.4.14|
|414||Request-URI Too Long||[RFC2616], Section 10.4.15|
|415||Unsupported Media Type||[RFC2616], Section 10.4.16|
|416||Requested Range Not Satisfiable||[RFC2616], Section 10.4.17|
|417||Expectation Failed||[RFC2616], Section 10.4.18|
|422||Unprocessable Entity||[RFC4918], Section 11.2|
|423||Locked||[RFC4918], Section 11.3|
|424||Failed Dependency||[RFC4918], Section 11.4|
|426||Upgrade Required||[RFC2817], Section 6|
|500||Internal Server Error||[RFC2616], Section 10.5.1|
|501||Not Implemented||[RFC2616], Section 10.5.2|
|502||Bad Gateway||[RFC2616], Section 10.5.3|
|503||Service Unavailable||[RFC2616], Section 10.5.4|
|504||Gateway Timeout||[RFC2616], Section 10.5.5|
|505||HTTP Version Not Supported||[RFC2616], Section 10.5.6|
|506||Variant Also Negotiates||[RFC2295], Section 8.1|
|507||Insufficient Storage||[RFC4918], Section 11.5|
|510||Not Extended||[RFC2774], Section 7|
Copyright © The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at email@example.com.