Basic Information On Web Sites HTTP Error

Basic Information On Web Sites HTTP Error

8 1228
14 Flares Twitter 1 Facebook 0 Google+ 0 StumbleUpon 12 LinkedIn 1 14 Flares ×

When we visit websites we see different types of message. We think it is error or something else. But if we know about this HTTP Errors we can understand more clearly.

Here I added basic HTTP Errors which we often see during website visiting.

502 Bad gateway:


A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server received an invalid response from an upstream server it accessed to fulfil the request.

413 Request entity too large:

The Web server/Web site thinks that the HTTP data stream sent by the client was simply too large i.e. too many bytes.

204 No Content:

Nothing found in the server

203 Non-Authoritative Information (Since HTTP/1.1):

The  information which showing in the server is not from the originalal server, but is gathered from a local or a third-party copy.

403 Forbidden:

The Web server thinks that the HTTP data stream sent by the client was correct but access to the resource identified by the URL is forbidden for some reason.

400 Bad Request:

The Web server thinks that the data stream sent by the client is not maintained HTTP protocol completely. So the Web server was unable to understand the request and process it.

404 Not Found:

The 404 Not Found is an error message. It means the web server is not found at this moment but the requested resource may be available again in the future.

410 Gone:

The Web server (running the Web site) thinks that the URL requested by the client is no longer available & it will be never found.

408 Request Timeout:

The Web server thinks that there has been too long an interval of time between the establishment of an IP connection between the client & the server so the server has dropped the connection.

4xx Client Error:

This class of HTTP status message indicates there is a problem or error at the client or user agent end.

415 Unsupported Media Type:

The Web server thinks that the HTTP data stream sent by the client identifies a URL resource whose actual media type does not match with the media type specified on the request or incompatible with the current data.

500 Internal server error:

The Web server encountered an unexpected problem that prevented it from fulfilling the request send by the client for access to the requested URL.

Do you any other website HTTP Errors? Share with us 

 

14 Flares Twitter 1 Facebook 0 Google+ 0 StumbleUpon 12 LinkedIn 1 14 Flares ×

8 COMMENTS

  1. You could certainly see your skills within the work you write. The world hopes for even more passionate writers such as you who are not afraid to mention how they believe. All the time follow your heart.

  2. Hey Ahsan,
    I think you took a good topic to share with your readers.
    I think you should have added more to it.
    Like 200 status : everything is OK and the request is fulfilled.
    404: when server encounters certain broken URLs
    403:Forbidden Access, we encounter such errors because the domain has blocked our IP address and does not allow you to access its resource.
    Hopefully, a web Proxy will help you get access to the site. I have successfully experimented it.
    There are many much more status codes to be discussed.
    But you can visit at http://en.wikipedia.org/wiki/List_of_HTTP_status_codes
    to know more about it.

    I appreciate your efforts in putting up a good article.

Leave a Reply

*

CommentLuv badge