Appendix D. HTTP Status Codes
HTTP status codes are grouped as shown in Table D-1.
Table D-1. HTTP Status Code Groupings
|
Code Range |
Response Meaning |
|---|---|
|
|
Informational |
|
|
Client request successful |
|
|
Client request redirected, further action necessary |
|
|
Client request incomplete |
|
|
Server error |
Table D-2 lists the HTTP status code constants
defined by the HttpServletResponse interface and
used as parameters to its setStatus( ) and
sendError( ) methods. The version number in the
last column refers to the HTTP protocol version that first defined
the status code. Servlet API 2.0 added constants for HTTP Version 1.1
status codes as specified in the proposed
standard RFC 2068; Servlet API 2.2 added status codes 416
and 417 as specified in the draft standard RFC
2616. Note that HTTP/1.1 status codes require an HTTP/1.1-compliant
browser.
For more information on HTTP, see the book Web Client Programming by Clinton Wong (O’Reilly). The latest HTTP/1.1 specification is available in RFC 2616 at http://www.ietf.org/rfc/rfc2616.txt.
Table D-2. HTTP Status Code Constants
|
Constant |
Code |
Default Message |
Meaning |
HTTP Version |
|---|---|---|---|---|
|
|
100 |
Continue |
The server has received the initial part of the request and the client can continue with the remainder of its request. |
1.1 |
|
|
101 |
Switching Protocols |
The server is willing to comply with the client’s request to switch protocols to the one specified in the request’s |
Get Java Servlet Programming, 2nd Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
