November 2011
Intermediate to advanced
320 pages
10h 18m
English
Section 10 of RFC 2616 lists nearly 50 status codes that a server may choose from when constructing a response. About 15 of these are used in real life, and the rest are used to indicate increasingly bizarre or unlikely states, such as “402 Payment Required” or “415 Unsupported Media Type.” Most of the RFC-listed states do not map cleanly to the behavior of modern web applications; the only reason for their existence is that somebody hoped they eventually would.
A few codes are worth memorizing because they are common or carry special meaning, as discussed below.
This range of status codes is used to indicate a successful completion of a request:
This is a normal response to a successful GET or POST. The ...
Read now
Unlock full access