HTTP Status/Error Code: Quick Reference

 

During your HTTP sessions, you’ll receive various numbered codes from Web servers.  When connected via HTTP, displays these codes in the log window.  Some codes represent errors.  Most others simply communicate the status of the connection. Here are brief explanations for the most common status and error codes.

 

 

Error or Status Code	Description
100 Series	Informational - These status codes indicate a provisional response. The client should be prepared to receive one or more 1xx responses before receiving a regular response.
100	Continue.
101	Switching protocols.
200 Series	Success - This class of status codes indicates that the server successfully accepted the client request.
200	Okay - The client request has succeeded  This status code indicates that the Web server has successfully processed the request
201	Created.
202	Accepted.
203	Non-authoritative information.
204	No content.
205	Reset content.
206	Partial content.
300 Series	Redirection - The client browser must take more action to fulfill the request. For example, the browser may have to request a different page on the server or repeat the request by using a proxy server.
302	Object moved.
304	Not modified. The client requests a document that is already in its cache and the document has not been modified since it was cached. The client uses the cached copy of the document, instead of downloading it from the server
307	Temporary redirect.
400 Series	Client Error - An error occurs, and the client appears to be at fault. For example, the client may request a page that does not exist, or the client may not provide valid authentication information.
400	Bad request.
401	Access denied.
403	Forbidden.
404	Not found. This error may occur if the file that you are trying to access has been moved or deleted.
404.0	File or directory not found.
404.1	Web site not accessible on the requested port.
405	HTTP verb used to access this page is not allowed (method not allowed).
406	Client browser does not accept the MIME type of the requested page.
407	Proxy authentication required.
412	Precondition failed.
413	Request entity too large.
414	Request-URL too long.
415	Unsupported media type.
416	Requested range not satisfiable.
417	Execution failed.
423	Locked error.
500 Series	Server Error - The server cannot complete the request because it encounters an error.
500	Internal server error.  You see this error message for a wide variety of server-side errors.
500.12	Application is busy restarting on the Web server. Indicates that you tried to load an ASP page while IIS was in the process of restarting the application. This message should disappear when you refresh the page. If you refresh the page and the message appears again, it may be caused by antivirus software that is scanning your Global.asa file.
500.13	Web server is too busy.
500.15	Direct requests for Global.asa are not allowed.
500.16	UNC authorization credentials incorrect. This error code is specific to IIS 6.0.
500.18	URL authorization store cannot be opened. This error code is specific to IIS 6.0.
500.100	Internal ASP error. You receive this error message when you try to load an ASP page that has errors in the code.
501	Header values specify a configuration that is not implemented.
502	Bad Gateway.  Web server received an invalid response while acting as a gateway or proxy. You receive this error message when you try to run a CGI script that does not return a valid set of HTTP headers.
503	Service unavailable. This error code is specific to IIS 6.0.
504	Gateway timeout.
505	HTTP version not supported.

 

 

 

 

Tags: HTTP status code