MAY"> MUST"> MUST NOT"> OPTIONAL"> RECOMMENDED"> REQUIRED"> SHALL"> SHALL NOT"> SHOULD"> SHOULD NOT"> ]> greenbytes GmbH

Hafenweg 16 MuensterNW48155 Germany julian.reschke@greenbytes.de http://greenbytes.de/tech/webdav/

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 ietf-http-wg@w3.org, which may be joined by sending a message with subject "subscribe" to ietf-http-wg-request@w3.org. Discussions of the HTTP working group are archived at . XML versions, latest edits and the issues list for this document are available from .

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 ).

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. The registry itself is maintained at .

No security considerations are introduced by this document beyond those already inherent in use of the referenced HTTP status codes.

of this specification provides updated registrations of HTTP status codes for the IANA registry at .

Thanks to authors of - Rohit Khare and Scott Lawrence - for the original specification.

Technische Universiteit Eindhoven

Postbus 513 Kamer HG 6.57 5600 MB Eindhoven (The Netherlands) koen@win.tue.nl

Hewlett-Packard Company

1501 Page Mill Road 3U-3 Palo Alto CA 94304 USA +1 415 857 4691 mutz@hpl.hp.com

Applications HTTP hypertext transfer protocol Microsoft Corporation

yarong@microsoft.com

Dept. Of Information and Computer Science, University of California, Irvine

ejw@ics.uci.edu

Netscape

asad@netscape.com

Novell

srcarter@novell.com

Novell

dcjensen@novell.com

University of California, Irvine

fielding@ics.uci.edu

W3C

jg@w3.org

Compaq Computer Corporation

mogul@wrl.dec.com

MIT Laboratory for Computer Science

frystyk@w3.org

Xerox Corporation

masinter@parc.xerox.com

Microsoft Corporation

paulle@microsoft.com

W3C

timbl@w3.org

Microsoft Corporation

1 Microsoft Way RedmondWA98052USA frystyk@microsoft.com

Microsoft Corporation

1 Microsoft Way RedmondWA98052USA paulle@microsoft.com

Agranat Systems, Inc.

5 Clocktower Place, Suite 400 MaynardMA01754USA lawrence@agranat.com

CommerceNet

2064 Edgewood Dr. Palo Alto CA 94303 US ldusseault@commerce.net

The table below contains an update to the IANA registry at . Value Description Reference 100Continue 101Switching Protocols 102Processing 200OK 201Created 202Accepted 203Non-Authoritative Information 204No Content 205Reset Content 206Partial Content 207Multi-Status 226IM Used 300Multiple Choices 301Moved Permanently 302Found 303See Other 304Not Modified 305Use Proxy 306(Reserved) 307Temporary Redirect 400Bad Request 401Unauthorized 402Payment Required 403Forbidden 404Not Found 405Method Not Allowed 406Not Acceptable 407Proxy Authentication Required 408Request Timeout 409Conflict 410Gone 411Length Required 412Precondition Failed 413Request Entity Too Large 414Request-URI Too Long 415Unsupported Media Type 416Requested Range Not Satisfiable 417Expectation Failed 422Unprocessable Entity 423Locked 424Failed Dependency 426Upgrade Required 500Internal Server Error 501Not Implemented 502Bad Gateway 503Service Unavailable 504Gateway Timeout 505HTTP Version Not Supported 506Variant Also Negotiates 507Insufficient Storage 510Not Extended