Pr.Pg Next Pg

Http Status Codes tutorials

  • When a Web server responds to a request from a browser or other Web client, the response typically consists of a status line, some response headers, a blank line, and the document. Here is a minimal example:

HTTP/1.1 200 OK

Content-Type: text/plain

Hello World

  • The status line consists of the HTTP version, an integer that is interpreted as a status code, and a very short message corresponding to the status code.

  • Below is a list of HTTP status codes and associated messages that might be returned from the Web Server:

 

Code:

Message:

Description:

100

Continue

Only a part of the request has been received by the server, but as long as it has not been rejected, the client should continue with the request

101

Switching Protocols

The server switches protocol.

200

OK

The request is OK

201

Created

The request is complete, and a new resource is created 

202

Accepted

The request is accepted for processing, but the processing is not complete.

203

Non-authoritative Information

The server successfully processed the request, but is returning information that may be from another source.

204

No Content

The server successfully processed the request, but isn’t returning any content. 

205

Reset Content

The server successfully oolean the request, but isn’t returning any content. Unlike a 204 response, this response requires that the requestor reset the document view (for instance, clear a form for new input).

206

Partial Content

The server successfully processed a partial GET request. 

300

Multiple Choices

A link list. The user can select a link and go to that location. Maximum five addresses  

301

Moved Permanently

The requested page has moved to a new url 

302

Found

The requested page has moved temporarily to a new url 

303

See Other

The requested page can be found under a different url 

304

Not Modified

You should configure your server to return this response (called the If-Modified-Since HTTP header) when a page hasn’t changed since the last time the requestor asked for it. This saves you bandwidth and overhead because your server can tell Googlebot that a page hasn’t changed since the last time it was crawled.

305

Use Proxy

The requestor can only access the requested page using a proxy. When the server returns this response, it also indicates the proxy that the requestor should use.

306

Unused

This code was used in a previous version. It is no longer used, but the code is reserved.

307

Temporary Redirect

The requested page has moved temporarily to a new url.

400

Bad Request

The server did not understand the request

401

Unauthorized

The requested page needs a username and a password

402

Payment Required

You cannot use this code yet

403

Forbidden

Access is forbidden to the requested page

404

Not Found

The server cannot find the requested page.

405

Method Not Allowed

The method specified in the request is not allowed.

406

Not Acceptable

The server can only generate a response that is not accepted by the client.

407

Proxy Authentication Required

You must authenticate with a proxy server before this request can be served.

408

Request Timeout

The request took longer than the server was prepared to wait.

409

Conflict

The request could not be completed because of a conflict.

410

Gone

The requested page is no longer available.

411

Length Required

The “Content-Length” is not defined. The server will not accept the request without it.

412

Precondition Failed

The precondition given in the request evaluated to false by the server.

413

Request Entity Too

Large

The server will not accept the request, because the request entity is too large.

414

Request-url Too Long

The server will not accept the request, because the url is too long. Occurs when you convert a “post” request to a “get” request with a long query information.

415

Unsupported Media

Type

The server will not accept the request, because the media type is not supported.

417

Expectation Failed

 

500

Internal Server Error

The request was not completed. The server met an unexpected condition

501

Not Implemented

The request was not completed. The server did not support the functionality required.

502

Bad Gateway

The request was not completed. The server received an invalid response from the upstream server

503

Service Unavailable

The request was not completed. The server is temporarily overloading or down.

504

Gateway Timeout

The gateway has timed out.

505

HTTP Version Not

Supported

The server does not support the “http protocol” version.

Pr.Pg border                                              Next Pg