Technical Intranet Errors Guide

Error Code	Explanation of Error	Solutions
400-Bad Request	The request could not be understood by the server due to malformed syntax.	The client SHOULD NOT repeat the request without modifications.
401- Unauthorized	The request requires user authentication.	The response MUST include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
403- Forbidden	The server understood the request, but is refusing to fulfill it. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.	Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity.
408 - Request Timeout	The client did not produce a request within the time that the server was prepared to wait.	The client MAY repeat the request without modifications at any later time.
411- Length Required	The server refuses to accept the request without a defined Content-Length.	The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
406 - Not Acceptable	The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.	The response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.
500 -Internal Server Error	The server encountered an unexpected condition, which prevented it from fulfilling the request.	500 Internal Server Error is a server-side error, meaning the problem probably isn't with your computer or Internet connection but instead is a problem with the web site's server. Reload the web page. You can do that by clicking the refresh/reload button, pressing F5, or trying the URL again from the address bar. Even if the 500 Internal Server Error is a problem on the web server, the issue may only be temporary. Trying the page again will often be successful
502- Bad Gateway	The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfil the request.	Since a 502 Bad Gateway error is usually directly related to a server problem there are three things to try when resolving the situation. Steps: Retry the action. Use the refresh button on your tool bar to attempt to reload the page. Come back again later. Sometimes a 502 Bad Gateway error is only a temporary problem of the website you may be trying to access.
503 -Service Unavailable	The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.	The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
504- Gateway Timeout	The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server it accessed in attempting to complete the request.	If you are a general user or visitor of that website, then you can follow these tip. -Wait until the server gets balanced -Use Wayback machine to get the cached copy of website -Use the Social medias for contacting the webmaster -Check whether it is your network problem -Check for malware presence in your browser
505 - HTTP Version Not Supported	The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.	The only option to fix this error is to upgrade the Web server software to the higher version. Because the lower versions provide poorer security and performance than newer versions of the protocol. If you are registered with 100pulse, your site will be monitored and you will be intimated by an email or a short message service when 505 status code error occurs
203- Non-Authoritative Information	The returned meta-information in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy.	The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource MAY result in a superset of the meta-information known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).
204 - No Content	The server has fulfilled the request but there is no new information to send back.	If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view. The response MAY include new meta-information in the form of entity-headers, which SHOULD apply to the document currently in the user agent's active view.
205 - Reset Content	The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent.	This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
304 - Not Modified	If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The response MUST NOT contain a message-body.	The response MUST include Date ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant
305 - Use Proxy	The requested resource MUST be accessed through the proxy given by the Location field.	The Location field gives the URL of the proxy. The recipient is expected to repeat the request via the proxy.
405- Method Not Allowed	The method specified in the Request-Line is not allowed for the resource identified by the Request-URI.	The response MUST include an Allow header containing a list of valid methods for the requested resource.
404 - Not Found	The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.	If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
410 - Gone	The requested resource is no longer available at the server and no forwarding address is known. This condition SHOULD be considered permanent.	Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.