HTTP status code in IIS 7.0 and IIS 7.5

Log File Location

By default, IIS 7.0 puts log files in the following folders:

Inetpub \ logs \ logfiles

This folder contains different directories for each web site. By default, log files are created daily in the directory and named by date. For example, the log file may be named as follows:

Ex Month/day/year . Log back to the top HTTP status Code

This section describes the HTTP status code used by IIS 7.0.

Note:This articleArticleEach possible HTTP status code is not listed, which must be in the HTTP specification. This article includes only HTTP status code that can be sent by IIS 7.0. For example, you can customize an Internet Server API (ISAPI) filter or a custom HTTP module to set your own HTTP status code.

1 Xx -Information

These HTTP status codes indicate temporary responses. One or more 1 received by the clientXxThe response client computer receives the regular response.

IIS 7.0 uses the following informative HTTP status code:

• 100-continue.
• 101-exchange protocol.

2 Xx -Successful

These HTTP status codes indicate that the server has successfully accepted the request.

IIS 7.0 uses the following successful HTTP status code:

• 200-OK. The client request has been successfully completed.
• 201-create.
• 202-accept.
• 203-no authoritative information.
• 204-NO content.
• 205-Reset content.
• 206-part of content.

3 Xx -Redirection

These HTTP status codes indicate that the client browser must take more measures to execute the request. For example, the client browser may have to request different pages on the server. Alternatively, the client browser may need to use the proxy server to repeat the request.

IIS 7.0 uses the following code to redirect HTTP status:

• 301-permanently deleted.
• 302-the object has been moved.
• 304-not modified.
• 307-temporary redirection.

4 Xx Client errors

The HTTP Status Code indicates that an error has occurred and the client browser displays as faulty. For example, a client browser may request a page that does not exist. Alternatively, the client browser may not provide valid authentication information.

IIS 7.0 uses the following client error HTTP status code:

• 400-request error. The request cannot be understood by the server due to incorrect syntax. The client should not repeat the request that has not been modified.

  IIS 7.0 defines the following HTTP status code to indicate a more specific cause of the 400 Error:

  • 400.1-invalid target header.
  • 400.2-invalid depth header.
  • 400.3-invalid if header.
  • 400.4-invalid overwrite header.
  • 400.5-invalid translation header.
  • 400.6-invalid request body.
  • 400.7-Invalid Content Length.
  • 400.8-the timeout is invalid.
  • 400.9-The lock tag is invalid.
• 401-Access denied.

  IIS 7.0 defines several HTTP status codes to indicate a more specific cause of the 401 error. The following specific HTTP status code is displayed in the client browser, but not in the IIS log:

  • 401.1-Logon Failed.
  • 401.2-Login Failed, server configuration.
  • 401.3-authorization to ACL resources.
  • 401.4-An error occurred while authorizing the filter.
  • 401.5-Authorization failed ISAPI/cgi applicationProgram.
• 403-Access prohibited.

  IIS 7.0 defines the following HTTP status code to indicate a more specific cause of the 403 error:

  • 403.1-the execution access is forbidden.
  • 403.2-Read access is forbidden.
  • 403.3-write access is disabled.
  • 403.4-required SSL.
  • 403.5-required SSL 128.
  • 403.6-rejected IP address.
  • 403.7-client certificate required.
  • 403.8-site access is denied.
  • 403.9-Access prohibited: too many clients attempt to connect to the web server.
  • 403.10-Access prohibited: the Web server is configured to reject access requests.
  • 403.11-Access prohibited: the password has been changed.
  • 403.12-The ing program rejects access.
  • 403.13-the client certificate is revoked.
  • 403.14-the directory list is denied.
  • 403.15-Access prohibited: the client access license has exceeded the limit on the Web server.
  • 403.16-the client certificate is untrusted or invalid.
  • 403.17-the client certificate has expired or has not yet taken effect.
  • 403.18-the request URL cannot be executed in the current application pool.
  • 403.19-the CGI application client cannot be executed in this application pool.
  • 403.20-Access prohibited: Passport Logon Failed.
  • 403.21-Access prohibited: the source access is denied.
  • 403.22-Access prohibited: reject unlimited depth.
  • 403.502-Access prohibited: too many requests come from the same client IP address. The dynamic IP address limit has been reached.
• 404-not found.

  IIS 7.0 defines the following HTTP status code to indicate a more specific 404 error cause:

  • 404.0-not found.
  • 404.1-no site found.
  • 404.2-Restrictions on ISAPI or CGI.
  • 404.3-MIME type restriction.
  • 404.4-No handler is configured.
  • 404.5-the request for filtering configuration is rejected.
  • 404.6-the verb is rejected.
  • 404.7-denied file extension.
  • 404.8-hide the namespace.
  • 404.9-hidden file attributes.
  • 404.10-the request header is too long.
  • 404.11-The request contains the escape sequence of double quotation marks.
  • 404.12-The request contains high-level characters.
  • 404.13-the content length is too large.
  • 404.14-the request URL is too long.
  • 404.15-the query string is too long.
  • 404.16-The dav request is sent to the static file handler.
  • 404.17- ing to dynamic content mapped by a static file handler using the wildcard mime.
  • 404.18-the query string sequence is rejected.
  • 404.19-rejected by filtering rules.
  • 404.20-URLs with too many segments
• 405-the method is not allowed.
• 406-the client browser does not accept the MIME type of the requested page.
• 408-request timeout.
• 412-precondition failed.

5 Xx -Server Error

These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

IIS 7.0 uses the following server error HTTP status code:

• 500-internal server error.

  IIS 7.0 defines the following HTTP status code to indicate a more specific cause of the 500 error:

  • 500.0-error in module or ISAPI.
  • 500.11-the application is shutting down the web server.
  • 500.12-the application is restarting the web server.
  • 500.13-the Web server is too busy.
  • 500.15-direct requests to global. asax are not allowed.
  • 500.19-the configuration data is invalid.
  • 500.21-unidentifiable modules.
  • 500.22-Asp. Net httpmodules configuration is not applicable to managed pipeline mode.
  • 500.23-Asp. Net httphandlers configuration is not applicable to managed pipeline mode.
  • 500.24-Asp. The. NET simulation configuration is not applicable to the managed pipeline mode.
  • 500.50 rq_begin_request indicates that a rewrite error occurs during processing. An error occurred while executing the configuration or inbound rules.Note:The following figure shows the read location in the distributed rule configuration for inbound and outbound rules.
  • The 500.51 gl_pre_begin_request notification contains a rewrite error during processing. A global configuration or rule execution error occurs.Note:The following describes how to read the global rule configuration.
  • 500.52 rq_send_response indicates that a rewrite error occurs during processing. An outbound rule execution occurs.
  • 500.53 rq_release_request_state indicates that a rewrite error occurs during processing. An error occurred while executing the outbound rule. All rules are configured to be executed before the output user cache obtains updates.
  • 500.100-Internal ASP error.
• 501 the header value specifies the unimplemented configuration.
• 502-when the web server acts as a gateway or proxy server, it receives an invalid response.

  IIS 7.0 defines the following HTTP status code to indicate a more specific cause of the 502 error:

  • 502.1-CGI application timeout.
  • 502.2-the gateway is invalid.
• 503-the service is unavailable.

  IIS 7.0 defines the following HTTP status code to indicate a more specific 503 error cause:

  • 503.0-application pool unavailable.
  • 503.2-the number of concurrent requests exceeds the limit.

Back to Top General HTTP status code and cause

Some common HTTP status codes are as follows:

• 200-OK. IIS 7.0 successfully processes the request.
• 304-not modified. The client browser request is in the cache and the document has not been modified after the document is cached. The client browser uses cached copies of this document instead of downloading the document from the server.
• 400-request error. The HTTP. SYS file prevents IIS 7.0 from processing requests because of a problem in the request. Generally, this HTTP status code indicates the characters contained in the request, invalid sequences, or conflicting security settings in the HTTP. SYS file.
• 401.1-Logon Failed. The logon attempt may fail because the user name or password is invalid. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942044Http://support.microsoft.com/kb/942044)Error message when you attempt to host a web application running on IIS 7.0: "HTTP Error 401.1-not found"
• 401.2-Login Failed, server configuration. The HTTP Status Code indicates that the authentication configuration on the server is incorrect. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942043Http://support.microsoft.com/kb/942043)When you try to access the web page on IIS 7.0, an error message is displayed: "HTTP Error 401.2-unauthorized"
• 401.3-authorization to ACL resources. This HTTP status code indicates a problem with NTFS file system permissions. This problem may occur even if the permission is correct for the file you are trying to access. For example, if the IUSR account does not have the permission to access the c: \ winnt \ system32 \ inetsrv directory, this problem occurs. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942042Http://support.microsoft.com/kb/942042)When you attempt to browse the Web page hosted by a server running IIS 7.0, the following error message is displayed: "HTTP Error 401.3-unauthorized"
• 401.4-An error occurred while authorizing the filter. Requests that are handled due to authorization issues that are not allowed by the ISAPI filter. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942079Http://support.microsoft.com/kb/942079)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 401.4-Failed authorization by filter"
• 401.5-Authorization failed ISAPI/cgi application. Requests that are handled due to authorization issues that are not allowed by ISAPI applications or general Gateway Interface (CGI) applications. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942078Http://support.microsoft.com/kb/942078)When you access the hosted web site on a computer running IIS 7.0, the error message is: "HTTP Error 401.5-Authorization failed, by each cgi isapi application"
• 403.1-the execution access is forbidden. An appropriate execution permission level is not granted. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942065Http://support.microsoft.com/kb/942065)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.1-Forbidden"
• 403.2-Read access is forbidden. The appropriate read permission level is not granted. Verify the directory to which you have set IIS 7.0 to grant read permission. In addition, if you use the default document, verify that the default document exists. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942036Http://support.microsoft.com/kb/942036)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.2-Access prohibited"
• 403.3-write access is forbidden. The appropriate write permission level is not granted. The permission to verify IIS 7.0 and NTFS file system are set to grant write permission to this directory. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942035Http://support.microsoft.com/kb/942035)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.3 -- disabled"
• 403.4-required SSL. Requests are sent through insecure channels. Web applications require Secure Sockets Layer (SSL) connections. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942070Http://support.microsoft.com/kb/942070)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.4-Access prohibited"
• 403.5-required SSL 128. The server is configured to require 128-bit SSL connections. However, requests are not sent by using 128-bit encryption. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942069Http://support.microsoft.com/kb/942069)When you attempt to browse the Web page hosted on IIS 7.0, an error message is displayed: "HTTP Error 403.5-Access prohibited"
• 403.6-rejected IP address. Configure the server as the current IP address that denies access. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942068Http://support.microsoft.com/kb/942068)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.6-IP address is denied"
• 403.7-client certificate required. The server is configured as the required client authentication certificate. However, the client browser does not have the corresponding client certificate installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942067Http://support.microsoft.com/kb/942067)When you attempt to run a web application running on the IIS 7.0 server, the following error message is displayed: "HTTP Error 403.7-Access prohibited"
• 403.8-site access is denied. Configure the server to reject requests based on the Domain Name System (DNS) name of the client computer. For details about how to solve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 942066Http://support.microsoft.com/kb/942066)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.8-Access prohibited"
• 403.12-The ing program rejects access. You need a client certificate to access this page. However, the user ID mapped to the client certificate is denied access to the file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942064Http://support.microsoft.com/kb/942064)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.12-client certificate rejected"
• 403.13-the client certificate is revoked. The client browser will try to use the client certificate that has been revoked by the certificate authority. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942063Http://support.microsoft.com/kb/942063)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.13-Access prohibited"
• 403.14-the directory list is rejected. The server is not configured to display the content directory list, and the default document is not set. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942062Http://support.microsoft.com/kb/942062)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.14-Access prohibited"
• 403.16-the client certificate is untrusted or invalid. The client browser will try to use a server with untrusted client certificate that is running IIS 7.0 or is invalid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942061Http://support.microsoft.com/kb/942061)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.16-Access prohibited"
• 403.17-the client certificate has expired or has not yet taken effect. The client browser will try to use the client certificate that has expired or is invalid. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942038Http://support.microsoft.com/kb/942038)When you try to access the Web page hosted on Internet Information Services 7.0, an error message is displayed: "HTTP Error 403.17 (Forbidden) client certificate has expired"
• 403.18-the request URL cannot be executed in the current application pool. Configure the custom error page and customize the error page to reside in different application pool than the requested URL application pool. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942037Http://support.microsoft.com/kb/942037)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.18-Access prohibited"
• 403.19-the client browser where the CGI application cannot be executed in this application pool. The application pool ID does not haveReplace Process-level tokensUser permissions. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942048Http://support.microsoft.com/kb/942048)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 403.19-Access prohibited"
• 404.0-not found. The file you are trying to access has been moved or does not exist. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942041Http://support.microsoft.com/kb/942041)When you try to open the web page hosted on IIS 7.0, an error message is displayed: "HTTP Error 404.0-cannot be found"
• 404.2-Restrictions on ISAPI or CGI. The requested ISAPI resource or CGI resource is on a restricted computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942040Http://support.microsoft.com/kb/942040)When you attempt to access the Web page hosted by IIS 7.0 on a computer, the following error message is displayed: "HTTP Error 404.2-cannot be found"
• 404.3-MIME type restriction. The current mime ing. The extension type used for the request is invalid or not configured. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942032Http://support.microsoft.com/kb/942032)When a user accesses a Web site hosted on a server running Internet Information Services 7.0, an error message is displayed: "HTTP Error 404.3-cannot be found"
• 404.4-No handler is configured. The file extension of the requested URL is not configured as a request handler on the Web server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942052Http://support.microsoft.com/kb/942052)When you access the website hosted on IIS 7.0, the error message is: "HTTP Error 404.4-cannot be found"
• 404.5-the request for filtering configuration is rejected. The requested URL contains a character sequence that is blocked by the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942053Http://support.microsoft.com/kb/942053)Error message when you access the hosted web site on IIS 7.0: "HTTP Error 404.5-URL sequence rejected"
• 404.6-the verb is rejected. The request is sent by using an unconfigured or invalid HTTP predicate. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942046Http://support.microsoft.com/kb/942046)Error message when you access the hosted web site on IIS 7.0: "HTTP Error 404.6-verb_denied"
• The denied 404.7 file extension. The requested file extension is not allowed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942045Http://support.microsoft.com/kb/942045)When you attempt to browse the Web page hosted on IIS 7.0, an error message is displayed: "HTTP Error 404.7-file_extension_denied"
• 404.8-hide the namespace. The requested URL is rejected because the directory is hidden. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942047Http://support.microsoft.com/kb/942047)When you try to access the web page on IIS 7.0, an error message is displayed: "HTTP Error 404.8-hidden_namespace"
• 404.9-hidden file attributes. The requested file is hidden. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942049Http://support.microsoft.com/kb/942049)Error message when you attempt to access the hosted web site on IIS 7.0: "HTTP Error 404.9-file property hiding"
• 404.10-the request header is too long. The request is rejected because the request header is too long. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942077Http://support.microsoft.com/kb/942077)Error message when you access the hosted web site on the Internet Information Services 7.0 server: "HTTP Error 404.10-request_header_too_long"
• 404.11-The request contains the escape sequence of double quotation marks. This request contains a double escape sequence. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942076Http://support.microsoft.com/kb/942076)Error message when you access the hosted web site on IIS 7.0: "HTTP Error 404.11-url_double_escaped"
• 404.12-The request contains high-level characters. The application contains high-level characters and the server is configured as not allowed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942075Http://support.microsoft.com/kb/942075)Error message when you access the hosted web site on IIS 7.0: "HTTP Error 404.12-url_has_high_bit_chars"
• 404.13-the content length is too large. The Content Length header contained in the request. The Content Length header value is greater than the server limit. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942074Http://support.microsoft.com/kb/942074)Error message when you access the hosted web site on the Internet Information Services 7.0 server: "HTTP Error 404.13-content_length_too_large"
• 404.14-the request URL is too long. The requested URL exceeds the server's limit. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942073Http://support.microsoft.com/kb/942073)Error message when you access the website hosted on IIS 7.0: "HTTP Error 404.14-url_too_long"
• 404.15-the query string is too long. The length of the query string contained in this request exceeds the limit allowed by the server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942071Http://support.microsoft.com/kb/942071)Error message when you access the hosted web site on the IIS 7.0 server: "HTTP Error 404.15-cannot be found"
• 404.17-the dynamic content mapped to the static file handler. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 2019689Http://support.microsoft.com/kb/2019689)When you access the website hosted on IIS 7.0, the error message is: "HTTP Error 404.17-cannot be found"
• 405.0-the method is not allowed. An invalid HTTP method is used to send a request. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942051Http://support.microsoft.com/kb/942051)When a user accesses a Web site hosted on a server running Internet Information Services 7.0, an error message is displayed: "HTTP Error 405.0-method not allowed"
• 406.0-invalid MIME type. An invalid accept header is used to send a request. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942050Http://support.microsoft.com/kb/942050)Error message when you access the hosted web site on the Internet Information Services 7.0 server: "HTTP Error 406-unacceptable"
• 412.0-precondition failed. The request is sent by using an invalid value that matches the request header. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942056Http://support.microsoft.com/kb/942056)When you access Internet Information Services (IIS) 7.0 on the website hosted by you, an error message is displayed: "HTTP Error 412-precondition failed"
• 500-internal server error. This HTTP status code may appear on the server for many reasons. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942031Http://support.microsoft.com/kb/942031)Error message when you access the website hosted on IIS 7.0: "HTTP Error 500.0-internal server error"
• 500.11-the application is shutting down the web server. The request cannot be processed because the target application pool is closed. Wait until the auxiliary process is closed and try again. If this problem persists, you may encounter a problem where the web application is blocked from closing the correct web application.
• 500.12-the application is restarting the web server. Because the target application pool is restarting, the request is not processed. When the page is refreshed, the HTTP status code should disappear. If the HTTP status code refresh the page again, the virus software that may cause the problem is scanning the global. Asa file. If this problem persists, you may encounter a problem where the web application is blocked from restarting the web application correctly.
• 500.13-the Web server is too busy. Because the server is too busy to accept any new incoming request, it will not process the request. Generally, this HTTP Status Code indicates that the number of incoming requests exceeds the number that can be processed by IIS 7.0 web applications. This problem may occur because the performance configuration settings will be too low, the hardware is insufficient, or a bottleneck occurs in the IIS 7.0 web application. A common troubleshooting method is to generate the IIS 7.0 process of the memory dump file when an error occurs, and then debug the memory dump file.
• 500.15-direct requests to global. asax are not allowed. Directly request the Global. Asa file or the Global. asax file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942030Http://support.microsoft.com/kb/942030)Error message when you access the hosted web site on IIS 7.0: "Global. Asa HTTP Error 500.15-direct request not allowed"
• 500.19-the configuration data is invalid. The HTTP status code appears because of problems in the associated applicationhost. config file or in the associated web. config file. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942055Http://support.microsoft.com/kb/942055)Error message when you access the website hosted on IIS 7.0: "HTTP Error 500.19-internal server error"
• 500.100-Internal ASP error. An error occurs during the processing of the Active Server Pages (ASP) page. To obtain specific error information, disable the friendly HTTP Error message in the Web browser. In addition, IIS logs may display ASP error numbers corresponding to errors. For more information about ASP error messages and the meaning of ASP error messages, click the following article number to view the article in the Microsoft Knowledge Base: 294271Http://support.microsoft.com/kb/294271)ASP error code
• 501.0-not implemented. The client browser sends the http trace verb and is not configured on the server to process the http trace verb. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942058Http://support.microsoft.com/kb/942058)When you access the hosted web site on IIS 7.0, the error message is: "HTTP Error 501.0-not implemented"
• 502.1-CGI application timeout. The CGI application does not return a valid HTTP response within the configured time limit. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942059Http://support.microsoft.com/kb/942059)Error message when you access the website hosted on IIS 7.0: "HTTP Error 502.1-network disconnection"
• 502.2-the gateway is invalid. The CGI application returns an invalid HTTP Response to the server running IIS 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 942057Http://support.microsoft.com/kb/942057)Error message when you access the website hosted on IIS 7.0: "HTTP Error 502.2-network disconnection"
• 503.0-the service is unavailable. This request is sent to the application pool that is currently stopped or disabled. To solve this problem, make sure the target application pool is started. Event Logs may provide information about why the application pool is stopped or disabled.
• 503.2-the number of concurrent requests exceeds the limit. "AppconcurrentrequestlimitProperty is set to a value lower than the current number of concurrent requests. IIS 7.0 does not allow more concurrent requestsAppconcurrentrequestlimitAttribute.

 

Http://support.microsoft.com/kb/943891

For more information about HTTP status code definitions, visit the following W3C Web site:

Http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10 Http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10)

Third-party Contact Information provided by Microsoft helps you find technical support. This contact information will be changed without notice. Microsoft cannot guarantee the accuracy of this third-party contact information.