File HttpErrorCodes.xml of Package vsn

<?xml version="1.0" encoding="ISO-8859-1"?>
<httpcode xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="Default">
 

  <code id="100">
               <type>  Informational </type>  
                <message> Continue. Not really an "error", this HTTP Status Code means everything is working fine.  </message> 
  </code> 
  <code id="101">
               <type>  Informational </type>  
                <message> Switching Protocols. Again, not really an "error", this HTTP Status Code means everything is working fine.  </message> 
  </code> 
  <code id="200">
               <type>  Successful </type>  
                <message> Success. This HTTP Status Code means everything is working fine. However, if you receive this message on screen, obviously something is not right... Please contact the server's administrator if this problem persists. Typically, this status code (as well as most other 200 Range codes) will only be written to your server logs.  </message> 
  </code> 
  <code id="201">
               <type>  Successful </type>  
                <message> Created. A new resource has been created successfully on the server.  </message> 
  </code> 
  <code id="202">
               <type>  Successful </type>  
                <message> Accepted. Request accepted but not completed yet, it will continue asynchronously.  </message> 
  </code> 
  <code id="203">
               <type>  Successful </type>  
                <message> Non-Authoritative Information. Request probably completed successfully but can't tell from original server.  </message> 
  </code> 
  <code id="204">
               <type>  Successful </type>  
                <message> No Content. The requested completed successfully but the resource requested is empty (has zero length).  </message> 
  </code> 
  <code id="205">
               <type>  Successful </type>  
                <message> Reset Content. The requested completed successfully but the client should clear down any cached information as it may now be invalid.  </message> 
  </code> 
  <code id="206">
               <type>  Successful </type>  
                <message> Partial Content. The request was canceled before it could be fulfilled. Typically the user gave up waiting for data and went to another page. Some download accelerator programs produce this error as they submit multiple requests to download a file at the same time.  </message> 
  </code> 
  <code id="300">
               <type>  Warning </type>  
                <message> Multiple Choices. The request is ambiguous and needs clarification as to which resource was requested.  </message> 
  </code> 
  <code id="301">
               <type>  Warning </type>  
                <message> Moved Permanently. The resource has permanently moved elsewhere, the response indicates where it has gone to.  </message> 
  </code> 
  <code id="302">
               <type>  Warning </type>  
                <message> Moved Temporarily. The resource has temporarily moved elsewhere, the response indicates where it is at present </message> 
  </code> 
  <code id="303">
               <type>  Warning </type>  
                <message> See Other/Redirect. A preferred alternative source should be used at present.  </message> 
  </code> 
  <code id="304">
               <type>  Warning </type>  
                <message> Not Modified. The server has identified from the request information that the client's copy of the information is up-to-date and the requested information does not need to be sent again.  </message> 
  </code> 
  <code id="305">
               <type>  Warning </type>  
                <message> Use Proxy. The request must be sent through the indicated proxy server.  </message> 
  </code> 
  <code id="307">
               <type>  Warning </type>  
                <message> Temporary Redirect The resource has temporarily moved elsewhere, the response indicates where it is at present. Client should still use this URL.  </message> 
  </code> 
  <code id="400">
               <type> ClientError </type>  
                <message> Bad Request. Due to malformed syntax, the request could not be understood by the server. The client should not repeat the request without modifications. Please contact the server's administrator if this problem persists.  </message> 
  </code> 
  <code id="401">
               <type> ClientError </type>  
			   <message> Unauthorized: The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource.  </message> 
  </code>   
  <code id="401.1">
               <type>  ClientError </type>  
                <message> Unauthorized: Logon Failed. This error indicates that the credentials passed to the server do not match the credentials required to log on to the server. Please contact the Web server's administrator to verify that you have permission to access the requested resource.  </message> 
  </code> 
  <code id="401.2">
               <type>  ClientError </type>  
                <message> Unauthorized: Logon Failed due to server configuration. This error indicates that the credentials passed to the server do not match the credentials required to log on to the server. This is usually caused by not sending the proper WWW-Authenticate header field. Please contact the Web server's administrator to verify that you have permission to access to requested resource.  </message> 
  </code> 
  <code id="401.3">
               <type>  ClientError </type>  
                <message> Unauthorized: Unauthorized due to ACL on resource. This error indicates that the credentials passed by the client do not have access to the particular resource on the server. This resource could be either the page or file listed in the address line of the client, or it could be another file on the server that is needed to process the file listed on the address line of the client. Please make a note of the entire address you were trying to access and then contact the Web server's administrator to verify that you have permission to access the requested resource.  </message> 
  </code> 
  <code id="401.4">
               <type>  ClientError </type>  
                <message> Unauthorized: Authorization failed by filter. This error indicates that the Web server has a filter program installed to verify users connecting to the server. The authentication used to connect to the server was denied access by this filter program. Please make a note of the entire address you were trying to access and then contact the Web server's administrator to verify that you have permission to access the requested resource.  </message> 
  </code> 
  <code id="401.5">
               <type>  ClientError </type>  
                <message> Unauthorized: Authorization failed by ISAPI/CGIapp. This error indicates that the address on the Web server you attempted to use has an ISAPI or CGI program installed that verifies user credentials before proceeding. The authentication used to connect to the server was denied access by this program. Please make a note of the entire address you were trying to access and then contact the Web server's administrator to verify that you have permission to access the requested resource.  </message> 
  </code> 
  <code id="403.1">
               <type>  ClientError </type>  
                <message> Forbidden: Execute Access Forbidden. This error can be caused if you try to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.2">
               <type>  ClientError </type>  
                <message> Forbidden: Read Access Forbidden. This error can be caused if there is no default page available and directory browsing has not been enabled for the directory, or if you are trying to display an HTML page that resides in a directory marked for Execute or Script permissions only. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.3">
               <type>  ClientError </type>  
                <message> Forbidden: Write Access Forbidden. This error can be caused if you attempt to upload to, or modify a file in, a directory that does not allow Write access. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.4">
               <type>  ClientError </type>  
                <message> Forbidden: SSL required. This error indicates that the page you are trying to access is secured with Secure Sockets Layer (SSL). In order to view it, you need to enable SSL by typing "HTTPs://" at the beginning of the address you are attempting to reach. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.5">
               <type>  ClientError </type>  
                <message> Forbidden: SSL 128 required. This error message indicates that the resource you are trying to access is secured with a 128-bit version of Secure Sockets Layer (SSL). In order to view this resource, you need a browser that supports this level of SSL. Please confirm that your browser supports 128-bit SSL security. If it does, then contact the Web server's administrator and report the problem.  </message> 
  </code> 
  <code id="403.6">
               <type>  ClientError </type>  
                <message> Forbidden: IP address rejected. This error is caused when the server has a list of IP addresses that are not allowed to access the site, and the IP address you are using is in this list. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.7">
               <type>  ClientError </type>  
                <message> Forbidden: Client certificate required. This error occurs when the resource you are attempting to access requires your browser to have a client Secure Sockets Layer (SSL) certificate that the server recognizes. This is used for authenticating you as a valid user of the resource. Please contact the Web server's administrator to obtain a valid client certificate.  </message> 
  </code> 
  <code id="403.8">
               <type>  ClientError </type>  
                <message> Forbidden: Site access denied. This error can be caused if the Web server is not servicing requests, or if you do not have permission to connect to the site. Please contact the Web server's administrator.  </message> 
  </code> 
  <code id="403.9">
               <type>  ClientError </type>  
                <message> Access Forbidden: Too many users are connected. This error can be caused if the Web server is busy and cannot process your request due to heavy traffic. Please try to connect again later. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.10">
               <type>  ClientError </type>  
                <message> Access Forbidden: Invalid Configuration. There is a configuration problem on the Web server at this time. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.11">
               <type>  ClientError </type>  
                <message> Access Forbidden: Password Change. This error can be caused if the user has entered the wrong password during authentication. Please refresh the page and try again. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="403.12">
               <type>  ClientError </type>  
                <message> Access Forbidden: Mapper Denied Access. Your client certificate map has been denied access to this Web site. Please contact the site administrator to establish client certificate permissions. You can also change your client certificate and retry, if appropriate.  </message> 
  </code> 
  <code id="403.13">
               <type>  ClientError </type>  
                <message> Client certificate revoked: The page you are trying to view requires the use of a valid client certificate. Your client certificate was revoked, or the revocation status could not be determined. The certificate is used for authenticating you as a valid user of the resource.  </message> 
  </code> 
  <code id="403.14">
               <type>  ClientError </type>  
                <message> Directory listing denied: This Virtual Directory does not allow contents to be listed.  </message> 
  </code> 
  <code id="403.15">
               <type>  ClientError </type>  
                <message> Client Access Licenses exceeded: There are too many people accessing the Web site at this time.  </message> 
  </code> 
  <code id="403.16">
               <type>  ClientError </type>  
                <message> Client certificate untrusted or invalid: The page you are trying to view requires the use of a valid client certificate. Your client certificate is untrusted or invalid. The client certificate is used for authenticating you as a valid user of the resource.  </message> 
  </code> 
  <code id="403.17">
               <type>  ClientError </type>  
                <message> Client certificate has expired or is not yet valid: The page you are trying to view requires the use of a valid client certificate. Your client certificate has expired or is not yet valid. The client certificate is used for identifying you as a valid user of the resource.  </message> 
  </code> 
  <code id="404">
               <type>  ClientError </type>  
                <message> Not Found: The Web server cannot find the file or script you asked for. Please check the URL to ensure that the path is correct. Please contact the server's administrator if this problem persists.  </message> 
  </code> 
  <code id="404.1">
               <type>  ClientError </type>  
                <message> Web site not found. (You can probably change the wording to read "Web site" instead of "Web server". The Web site you are looking for is unavailable due to its identification configuration settings.)  </message> 
  </code> 
  <code id="405">
               <type>  ClientError </type>  
                <message> Method Not Allowed: The method specified in the Request Line is not allowed for the resource identified by the request. Please ensure that you have the proper MIME type set up for the resource you are requesting. Please contact the server's administrator if this problem persists.  </message> 
  </code> 
  <code id="406">
               <type>  ClientError </type>  
                <message> Not Acceptable: The resource identified by the request can only generate response entities that have content characteristics that are "not acceptable" according to the Accept headers sent in the request. Please contact the server's administrator if this problem persists.  </message> 
  </code> 
  <code id="407">
               <type>  ClientError </type>  
                <message> Proxy Authentication Required: You must authenticate with a proxy server before this request can be serviced. Please log on to your proxy server, and then try again. Please contact the Web server's administrator if this problem persists.  </message> 
  </code> 
  <code id="408">
               <type>  ClientError </type>  
                <message> Request Time-Out. The client did not send a request within the required time period.  </message> 
  </code> 
  <code id="409">
               <type>  ClientError </type>  
                <message> Conflict. There is an internal conflict of access to the resource. Please contact the server's administrator if this problem persists.  </message> 
  </code> 
  <code id="410">
               <type>  ClientError </type>  
                <message> Gone. The requested resource used to be on the server but is no longer available. Any robot seeing this response should delete the reference from its information store.  </message> 
  </code> 
  <code id="411">
               <type>  ClientError </type>  
                <message> Length Required. The request requires the Content-Length HTTP request field to be specified.  </message> 
  </code> 
  <code id="412">
               <type>  ClientError </type>  
                <message> Precondition Failed: The precondition given in one or more of the Request-header fields evaluated to FALSE when it was tested on the server. The client placed preconditions on the current resource meta-information (header field data) to prevent the requested method from being applied to a resource other than the one intended. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="413">
               <type>  ClientError </type>  
                <message> Request Entity Too Large. The URL is too long (possibly too many query strings?).  </message> 
  </code> 
  <code id="414">
               <type>  ClientError </type>  
                <message> Request-URI Too Long: The server is refusing to service the request because the Request-URI is too long. This rare condition is likely to occur only in the following situations: A client has improperly converted a POST request to a GET request with long query information. A client has encountered a redirection problem (for example, a redirected URL prefix that points to a suffix of itself). The server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI. Please contact the Web server's administrator if this problem persists.  </message> 
  </code> 
  <code id="415">
               <type>  ClientError </type>  
                <message> Unsupported Media Type. The server does not support the resource type requested. Frequently found when attempting to serve up content which may require a plug-in. See also: Mime Types  </message> 
  </code> 
  <code id="416">
               <type>  ClientError </type>  
                <message> Requested Range Not Satisfiable. The portion of the resource requested is not available or out of range.  </message> 
  </code> 
  <code id="417">
               <type>  ClientError </type>  
                <message> Expectation Failed. The Expect specifier in the HTTP request header can not be met.  </message> 
  </code> 
  <code id="500">
               <type> ServerError </type>  
                <message> Internal Server Error: The Web server is incapable of performing the request. Please try your request again later. Please contact the Web server's administrator if this problem persists.  </message> 
  </code> 
  <code id="500.12">
               <type>  ServerError </type>  
                <message> Application restarting: There is a problem with the page you are trying to reach and it cannot be displayed.  </message> 
  </code> 
  <code id="500.13">
               <type>  ServerError </type>  
                <message> Server too busy: There is a problem with the page you are trying to reach and it cannot be displayed.  </message> 
  </code> 
  <code id="500.15">
               <type>  ServerError </type>  
                <message> Requests for Global.asa not allowed: There is a problem with the page you are trying to reach and it cannot be displayed.  </message> 
  </code> 
  <code id="500-100.asp">
               <type>  ServerError </type>  
                <message> ASP error: There is a problem with the page you are trying to reach and it cannot be displayed.  </message> 
  </code> 
  <code id="501">
               <type>  ServerError </type>  
                <message> Not Implemented: The Web server does not support the functionality required to fulfill the request. Please check your URL for errors, and contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="502">
               <type>  ServerError </type>  
                <message> Bad Gateway: The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. Please contact the Web server's administrator if the problem persists.  </message> 
  </code> 
  <code id="503">
               <type> ServerError </type>  
                <message> Out of Resources. Service temporarily unavailable - typically because it is currently overloaded.  </message> 
  </code> 
  <code id="504">
               <type>  ServerError </type>  
                <message> Gateway Time-Out: Unable to connect to origin web server. The web site you are attempting to access is currently unreachable. This may be due to a network outage, or the web site might be experiencing technical difficulties.  </message> 
  </code> 
  <code id="505">
               <type>  ServerError </type>  
                <message> HTTP Version not supported. The request uses a version of HTTP that is not supported.  </message> 
  </code> 


 
 
 
 
</httpcode>