Who knows about the 404 error !! Do you know of any other errors like this ??

Many of us spend many hours on the internet. Then we will sometimes see interruptions like Error / Not Responding. What is deeply ingrained in it is 404 Page not Responding. These will be defined as HTTP Response Status code. These are divided into 5 types.

1. Informational responses (100–199),
2. Successful responses (200–299),
3. Redirects (300–399),
4. Client errors (400–499),
5. Server errors (500–599).

1. Information responses

100 Continue
This interim response indicates that everything thus far is OK which the client should continue the request, or ignore the response if the request is already finished.
101 Switching Protocol
This code is shipped in response to upgrade request header from the client, and indicates the protocol the server is switching to.
102 Processing (WebDAV)
This code indicates that the server has received and is processing the request, but no response is out there yet.
103 Early Hints
This status code is primarily intended to be used with the Link header, letting the user agent start preloading resources while the server prepares a response.

2. Successful responses

200 OK
The request has succeeded. The meaning of the success depends on the HTTP method:
GET: The resource has been fetched and is transmitted within the message body.
HEAD: The entity headers are within the message body.
PUT or POST: The resource describing the results of the action is transmitted within the message body.
TRACE: The message body contains the request message as received by the server.
201 Created
The request has succeeded and a replacement resource has been created as a result. This is often typically the response sent after POST requests, or some PUT requests.
202 Accepted
The request has been received but not yet acted upon. It’s noncommittal, since there’s no way in HTTP to later send an asynchronous response indicating the result of the request. It’s intended for cases where another process or server handles the request, or for execution.
203 Non-Authoritative Information
This response code means the returned meta-information isn’t precisely the same as is out there from the origin server, but is collected from an area or a third-party copy. This is often mostly used for mirrors or backups of another resource. Apart from that specific case, the “200 OK” response is preferred to the present status.
204 No Content
There is no content to call this request, but the headers could also be useful. The user-agent may update its cached headers for this resource with the new ones.
205 Reset Content
Tells the user-agent to reset the document which sent this request.
206 Partial Content
This response code is employed when the Range header is shipped from the client to request only a part of a resource.
207 Multi-Status (WebDAV)
Conveys information about multiple resources, for situations where multiple status codes could be appropriate.
208 Already Reported (WebDAV)
Used inside a response element to avoid repeatedly enumerating the interior members of multiple bindings to an equivalent collection.
226 IM Used (HTTP Delta encoding)
The server has fulfilled a GET request for the resource, and therefore, the response may is a representation of the results of one or more instance-manipulations applied to the present instance.

Redirection messages

300 Multiple Choice
The request has quite one possible response. The user-agent or user should choose one among them. (There is not any standardized way of selecting one among the responses, but HTML links to the chances are recommended therefore the user can pick.)
301 Moved Permanently
The URL of the requested resource has been changed permanently. The new URL is given within the response.
302 Found
This response code means the URI of requested resource has been changed temporarily. Further, changes within the URI could be made within the future. Therefore, this same URI should be employed by the client in future requests.
303 See Other
The server sent this response to direct the client to urge the requested resource at another URI with a GET request.
304 Not Modified
This is used for caching purposes. It tells the client that the response has not been modified, therefore the client can still use an equivalent cached version of the response.
305 Use Proxy
Defined during a previous version of the HTTP specification to point that a requested response must be accessed by a proxy. It’s been deprecated thanks to security concerns regarding in-band configuration of a proxy.
306 unused
This response code is not any longer used; it’s just reserved. It had been utilized in a previous version of the HTTP/1.1 specification.
307 Temporary Redirect
The server sends this response to direct the client to urge the requested resource at another URI with same method that was utilized in the prior request. This has an equivalent semantics because the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was utilized in the primary request, a POST must be utilized in the second request.
308 Permanent Redirect
This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. This has an equivalent semantics because the 301 Moved Permanently HTTP response code, with the exception that the user agent must not change the HTTP method used: If a POST was utilized in the primary request, a POST must be utilized in the second request.

Client error responses

400 Bad Request
The server couldn’t understand the request thanks to invalid syntax.
401 Unauthorized
Although the HTTP standard specifies “unauthorized”, semantically this response means “unauthenticated.” That is, the client must authenticate itself to urge the requested response.
402 Payments Required
This response code is reserved for future use. The initial aim for creating this code was using it for digital payment systems, however, this status code is employed very rarely and no standard convention exists.
403 Forbidden
The client doesn’t have access rights to the content; that’s, it’s unauthorized, therefore the server is refusing to offer the requested resource. Unlike 401, the client’s identity is understood to the server.
404 Not Found
The server can’t find the requested resource. Within the browser, this suggests the URL isn’t recognized. In an API, this will also mean that the endpoint is valid but the resource itself doesn’t exist. Servers can also send this response rather than 403 to cover the existence of a resource from an unauthorized client. This response code is perhaps the foremost famous one thanks to its frequent occurrence on the online.
405 Method Not Allowed
The request method is understood by the server but has been disabled and can’t be used. For instance, an API may forbid DELETE-ing a resource. The two mandatory methods, GET and HEAD, must not ever be disabled and will not return this error code.
406 Not Acceptable
This response is shipped when the online server, after performing server-driven content negotiation, doesn’t find any content that conforms to the standards given by the user agent.
407 Proxy Authentication Required
This is almost like 401 but authentication is required to be done by a proxy.
408 Request Timeout
This response is shipped on an idle connection by some servers, even with none previous requests by the client. It means the server would really like to pack up this unused connection. This response is employed far more since some browsers, like Chrome, Firefox 27+, or IE9, use HTTP pre-connection mechanisms to hurry up surfing. Also note that some servers merely pack up the connection without sending this message.
409 Conflict
This response is shipped when an invitation conflicts with the present state of the server.
410 Gone
This response is shipped when the requested content has been permanently deleted from server with not forwarding address. Clients are expected to get rid of their caches and links to the resource. The HTTP specification intends this status code to be used for “limited-time, promotional services.” APIs shouldn’t feel compelled to point resources that are deleted with this status code.
411 Lengths Required
Server rejected the request because the Content-Length header field isn’t defined and therefore, the server requires it.
412 Precondition Failed
The client has indicated preconditions in its headers which the server doesn’t meet.
413 Payload overlarge
Request entity is larger than limits defined by server; the server might close the connection or return a Retry-After header field.
414 URI Too Long
The URI requested by the client is longer than the server is willing to interpret.
415 Unsupported Media Type
The media format of the requested data isn’t supported by the server, therefore the server is rejecting the request.
416 Range Not Satisfiable
The range specified by the Range header field within the request cannot be fulfilled; it’s possible that the range is outside the dimensions of the target URI’s data.
417 Expectations Failed
This response code means the expectation indicated by the Expect request header field cannot be met by the server.
418 I’m a teapot
The server refuses the plan to brew coffee with a teapot.
421 Misdirected Request
The request was directed at a server that’s unable to supply a response. This will be sent by a server that’s not configured to supply responses for the mixture of scheme and authority that is included within the request URI.
422 Unprocessable Entity (WebDAV)
The request was well-formed but was unable to be followed thanks to semantic errors.
423 Locked (WebDAV)
The resource that’s being accessed is locked.
424 Failed Dependency (WebDAV)
The request failed thanks to failure of a previous request.
425 Too Early
Indicates that the server is unwilling to risk processing an invitation which may be replayed.
426 Upgrade Required
The server refuses to perform the request using the present protocol but could be willing to try to so after the client upgrades to a special protocol. The server sends an Upgrade header during a 426 response to point the specified protocol(s).
428 Precondition Required
The origin server requires the request to be conditional. This response is meant to stop the ‘lost update’ problem, where a client GETs a resource’s state, modifies it, and PUTs it back to the server, when meanwhile a 3rd party has modified the state on the server, resulting in a conflict.
429 Too Many Requests
The user has sent too many requests during a given amount of your time (“rate limiting”).
431 Request Header Fields overlarge
The server is unwilling to process the request because its header fields are overlarge. The request could also be resubmitted after reducing the dimensions of the request header fields.
451 Unavailable For Legal Reasons
The user-agent requested a resource that can’t legally be provided, like an internet page censored by a government.

Server error responses

500 Internal Server Error
The server has encountered a situation it doesn’t skills to handle.
501 Not Implemented
The request method isn’t supported by the server and can’t be handled. The sole methods that servers are required to support (and therefore that has got not to return this code) are GET and HEAD.
502 Bad Gateway
This error response means the server, while working as a gateway to urge a response needed to handle the request, got an invalid response.
503 Service Unavailable
The server isn’t able to handle the request. Common causes are a server that’s down for maintenance or that’s overloaded. Note that alongside this response, a user-friendly page explaining the matter should be sent. These responses should be used for temporary conditions, and therefore, the Retry-After: HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also lookout about the caching-related headers that are sent alongside this response, as these temporary condition responses should usually not be cached.
504 Gateway Timeout
This error response is given when the server is acting as a gateway and can’t get a response in time.
505 HTTP Version Not Supported
The HTTP version utilized in the request isn’t supported by the server.
506 Variant Also Negotiates
The server has an indoor configuration error: the chosen variant resource is configured to interact in transparent content negotiation itself, and is therefore not a correct end point within the negotiation process.
507 Insufficient Storage (WebDAV)
The method couldn’t be performed on the resource because the server is unable to store the representation needed to successfully complete the request.
508 Loop Detected (WebDAV)
The server detected an infinite loop while processing request.
510 Not Extended
Further extensions to the request are required for the server to fulfil it.
511 Network Authentication Required
The 511-status code indicates that the client must authenticate to realize network access.

These are just some common HTTP Response Status that can occur on the Internet. Knowing this, we will browse the internet without any tracks!