The HTTP status codes in IIS 7.0 and in IIS 7.5


This table Contains The HTTP Status codes for IIS 7.0 and in IIS 7.5

IIS 7.0 uses the following informational HTTP status codes:
100 Continue.
101 Switching protocols.

IIS 7.0 uses the following success HTTP status codes:
200 OK. The client request has succeeded.
201 Created.
202 Accepted.
203 Nonauthoritative information.
204 No content.
205 Reset content.
206 Partial content.
IIS 7.0 uses the following redirection HTTP status codes:
301 Moved permanently.
302 Object moved.
304 Not modified.
307 Temporary redirect.
IIS 7.0 uses the following client error HTTP status codes:
400.1 Invalid Destination Header.
400.2 Invalid Depth Header.
400.3 Invalid If Header.
400.4 Invalid Overwrite Header.
400.5 Invalid Translate Header.
400.6 Invalid Request Body.
400.7 Invalid Content Length.
400.8 Invalid Timeout.
400.9 Invalid Lock Token.
IIS 7.0 defines several HTTP status codes that indicate a more specific cause of a 401 error.
401 Access denied.
401.1 Logon failed.
401.2 Logon failed due to server configuration.
401.3 Unauthorized due to ACL on resource.
401.4 Authorization failed by filter.
401.5 Authorization failed by ISAPI/CGI application.
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 403 error:
403 Forbidden.
403.1 Execute access forbidden.
403.2 Read access forbidden.
403.3 Write access forbidden.
403.4 SSL required.
403.5 SSL 128 required.
403.6 IP address rejected.
403.7 Client certificate required.
403.8 Site access denied.
403.9 Forbidden: Too many clients are trying to connect to the Web server.
403.10 Forbidden: Web server is configured to deny Execute access.
403.11 Forbidden: Password has been changed.
403.12 Mapper denied access.
403.13 Client certificate revoked.
403.14 Directory listing denied.
403.15 Forbidden: Client access licenses have exceeded limits on the Web server.
403.16 Client certificate is untrusted or invalid.
403.17 Client certificate has expired or is not yet valid.
403.18 Cannot execute requested URL in the current application pool.
403.19 Cannot execute CGI applications for the client in this application pool.
403.20 Forbidden: Passport logon failed.
403.21 Forbidden: Source access denied.
403.22 Forbidden: Infinite depth is denied.
403.502 Forbidden: Too many requests from the same client IP; Dynamic IP Restriction limit reached.
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 404 error:
404 Not found.
404.0 Not found.
404.1 Site Not Found.
404.2 ISAPI or CGI restriction.
404.3 MIME type restriction.
404.4 No handler configured.
404.5 Denied by request filtering configuration.
404.6 Verb denied.
404.7 File extension denied.
404.8 Hidden namespace.
404.9 File attribute hidden.
404.10 Request header too long.
404.11 Request contains double escape sequence.
404.12 Request contains high-bit characters.
404.13 Content length too large.
404.14 Request URL too long.
404.15 Query string too long.
404.16 DAV request sent to the static file handler.
404.17 Dynamic content mapped to the static file handler via a wildcard MIME mapping.
404.18 Querystring sequence denied.
404.19 Denied by filtering rule.
404.20 Too Many URL Segments
405 Method Not Allowed.
406 Client browser does not accept the MIME type of the requested page.
408 Request timed out.
412 Precondition failed.
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 500 error:
500 Internal server error.
500.0 Module or ISAPI error occurred.
500.11 Application is shutting down on the Web server.
500.12 Application is busy restarting on the Web server.
500.13 Web server is too busy.
500.15 Direct requests for Global.asax are not allowed.
500.19 Configuration data is invalid.
500.21  Module not recognized.
500.22 An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
500.23 An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
500.24 An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
500.50  A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
500.51 A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
500.52 A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
500.53 A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
500.100 Internal ASP error.
501 Header values specify a configuration that is not implemented.
502 Web server received an invalid response while acting as a gateway or proxy.
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 502 error:
502.1 CGI application timeout.
502.2 Bad gateway.
IIS 7.0 defines the following HTTP status codes that indicate a more specific cause of a 503 error:
503 Service unavailable.
503.0 Application pool unavailable.
503.2 Concurrent request limit exceeded.

Thank you for reading.

Advertisements

About rodvars
Been working in IT Services/Consulting for the past 15 years. My main areas of work are planning, development, managing and administration System infrastructures focusing on optimizing user processes, enforcing business security, performance enhancements, high availabilty and infrastucture scalability.

One Response to The HTTP status codes in IIS 7.0 and in IIS 7.5

  1. auto repair says:

    Hi there, just become aware of your weblog via Google, and found that it is really informative. I am gonna watch out for brussels. I will appreciate if you continue this in future. Numerous other folks can be benefited out of your writing. Cheers!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: