Java Reference
In-Depth Information
A
PPENDIX
G: HTTP R
ESPONSE
C
ODES
There are many different HTTP responses. This appendix lists them. This data was taken
from WikiPedia (
http://www.wikipedia.org
).
1xx Informational
Request received, continuing process.
• 100: Continue
• 101: Switching Protocols
2xx Success
The action was successfully received, understood, and accepted.
• 200: OK
• 201: Created
• 202: Accepted
• 203: Non-Authoritative Information
• 204: No Content
• 205: Reset Content
• 206: Partial Content
• 207: Multi-Status
For use with XML-based responses when a number of actions could have been request-
ed; details of the separate statuses are given in the message body.
3xx Redirection
The client must take additional action to complete the request.
• 300: Multiple Choices
• 301: Moved Permanently
This and all future requests should be directed to another URL.
• 302: Found
This is the most popular redirect code, but also an example of industrial practice con-
tradicting the standard. HTTP/1.0 specification (RFC 1945) required the client to perform
temporary redirect (the original describing phrase was "Moved Temporarily"), but popular
browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303
and 307 to disambiguate between the two behaviors. However, majority of Web applications
and frameworks still use the 302 status code as if it were the 303.
• 303: See Other (since HTTP/1.1)
The response to the request can be found under another URL using a GET method.
