Prentice Hall and Sun Microsystems. Personal use only; do not redistribute.

6.2 HTTP 1.1 Status Codes and Their Purpose

127

However, you should note that servers are allowed to vary the messages

slightly, and clients pay attention only to the numeric value. So, for example,

you might see a server return a status line of 

HTTP/1.1 200 Document Fol 

lows

 instead of 

HTTP/1.1 200 OK

.

100 (Continue)

If the server receives an 

Expect

 request header with a value of 

100 continue

, it means that the client is asking if it can send an 

attached document in a follow up request. In such a case, the server 

should either respond with status 100 (

SC_CONTINUE

) to tell the client 

to go ahead or use 417 (

Expectation Failed

) to tell the browser it 

won't accept the document. This status code is new in HTTP 1.1. 

101 (Switching Protocols)

A 101 (

SC_SWITCHING_PROTOCOLS

) status indicates that the server will 

comply with the 

Upgrade

 header and change to a different protocol. 

This status code is new in HTTP 1.1. 

200 (OK)

A value of 200 (

SC_OK

) means that everything is fine. The document fol 

lows for 

GET

 and 

POST

 requests. This status is the default for servlets; if 

you don't use 

setStatus

, you'll get 200. 

201 (Created)

A status code of 201 (

SC_CREATED

) signifies that the server created a 

new document in response to the request; the 

Location

 header should 

give its URL. 

202 (Accepted)

A value of 202 (

SC_ACCEPTED

) tells the client that the request is being 

acted upon, but processing is not yet complete. 

203 (Non Authoritative Information)

A 203 (

SC_NON_AUTHORITATIVE_INFORMATION

) status signifies that the 

document is being returned normally, but some of the response headers 

might be incorrect since a document copy is being used. This status 

code is new in HTTP 1.1. 

Second edition of this book: www.coreservlets.com; Sequel: www.moreservlets.com.

Servlet and JSP training courses by book's author: courses.coreservlets.com.