HTTP Server Status Codes

Successful Transactions

200

The request was successfully completed.

201

The request was a POST (or PUT) method and was successfully completed. 201 indicates that data were sent to the server and the server created a new resource as a result of the request.

202

The request is accepted for processing, but results of the processing are unknown.

203

The GET (or HEAD) request was fulfilled, but has returned partial information.

204

The request is fulfilled, but there is no new information to send the client.

Redirection Transactions

300

The requested resource is available from more than one location but the client and server could not negotiate a preferred choice.

301

The data requested have been permanently moved to a new URL.

302

The data were found but reside at a different URL. Users may get a 302 redirection is a URL pointing to a directory is missing the trailing slash character.

304

A GET request was sent that contained the "If-Modified-Since" field. The server found that the document had not been modified since the date specified.

Error Messages

400

Request syntax was wrong

401

Probably an authentication or access rights problem

Request required "Authorization" field that client did not specify. This may be an authentication problem between IIS and the client browser. Related sub-status codes are as follows:

HTTP 401.1: Denied by invalid user credentials
HTTP 401.2: Denied by server configuration
HTTP 401.3: Denied by resource ACL
HTTP 401.4: Denied by custom ISAPI filter
HTTP 401.5: Denied by custom ISAPI/CGI Web application

For comprehensive troubleshooting information, see:

 Troubleshooting HTTP 401 errors in IIS

402

Targeted operation costs money and client did not pay.

403

The requested resource is forbidden.

404

Server cannot find the requested URL.

405

Client attempted access using a method that is not allowed.

406

Resource found but not delivered because type is incompatible with types indicated by "accept" and "accepted-encoding" headers sent to server.

407

Proxy authentication required.

408

Request timeout.

409

Conflict. You may get a 409 error if you try to upload a file to your web server which is older than the one already there

410

Resource no longer available and no forwarding information found.

500

Server encountered internal error and cannot continue.

501

Legal request, but unsupported by the particular server.

502

A secondary server or gateway did not return a valid response to the server being tasked by the client.

503

Service unavailable. Server busy.

504

A secondary server or gateway took too long to respond to the server being tasked by the client.