This appendix lists the Internet status codes that can be returned in a response by a server.
The following are the numeric codes that may be returned as Internet Status and error codes in the Oracle Load Testing Autopilot and the Oracle OpenScript Resource Validation test.
The client can continue the request to the server.
The server has changed the application protocol being used on this connection at the request of the client via the Upgrade message header field.
The request completed successfully.
The request has been fulfilled and resulted in a new resource being created.
The request has been accepted for processing, but the processing has not been completed.
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 server has fulfilled the request but does not need to return new information.
The server has fulfilled the request and the client should reset the document view which caused the request to be sent to allow the user to initiate another input action.
The server has fulfilled the partial GET request for the resource.
The requested resource corresponds to ambiguous or multiple choices.
The requested resource has been assigned a new permanent Uniform Resource Identifier (URI) and any future references to the resource should use one of the returned URIs.
The requested resource resides temporarily under a different Uniform Resource Identifier (URI).
The response to the request can be found under a different Uniform Resource Identifier (URI) and should be retrieved using a GET method on that resource.
The client requested a resource that has not been modified.
The requested resource must be accessed through the proxy given by the Location field.
Used in a previous version of the HTTP specification but is no longer used and the code is reserved.
The requested resource resides temporarily under a different Uniform Resource Identifier (URI).
The request could not be understood by the server due to invalid syntax.
The requested resource requires user authentication.
Not implemented. Reserved for future use.
The server understood the request, but is refusing to fulfill it.
The server has not found anything matching the Request-URI (Uniform Resource Identifier).
The method in the Request-Line is not allowed for the resource identified by the Request-URI.
The response from the request has content characteristics that are not acceptable to the accept headers sent by the client.
407 Proxy Authentication Required
The client must first authenticate itself with the proxy.
The client did not produce a request within server timeout limit.
The request could not be completed due to a conflict with the current state of the resource. The user should resolve the conflict and resubmit the request.
The requested resource is no longer available at the server and no forwarding address is known.
The server refuses to accept the request without a defined Content-Length.
The precondition given in one or more of the request-header fields evaluated False when tested on the server.
The server is refusing to process a request because the request entity is larger than the server is willing or able to process.
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
416 Requested Range Not Satisfiable
A request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field.
The expectation given in an Expect request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server does not support the functionality required to fulfill the request.
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.
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server.
The server, while acting as a gateway or proxy, did not receive a time out while waiting for a response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
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.
This section lists the Internet, FTP, Gopher, and HTTP API error codes.
No more Internet handles could be generated at this time.
The request has timed out.
An extended error was returned from the server. This is typically a string or buffer containing a verbose error message.
An internal error has occurred.
The Uniform Resource Locator (URL) is invalid.
The Uniform Resource Locator (URL) scheme could not be recognized or is not supported.
The server name could not be resolved.
The requested protocol could not be located.
A request to InternetQueryOption or InternetSetOption specified an invalid option value.
The length of an option supplied to InternetQueryOption or InternetSetOption is incorrect for the type of option specified.
The request option cannot be set, only queried.
The Win32 Internet function support is being shut down or unloaded.
The request to connect and log on to an FTP server could not be completed because the supplied user name is incorrect.
The request to connect and log on to an FTP server could not be completed because the supplied password is incorrect.
The request to connect to and log on to an FTP server failed.
The requested operation is invalid.
The operation was canceled, usually because the handle on which the request was operating was closed before the operation completed.
The type of handle supplied is incorrect for this operation.
The requested operation cannot be carried out because the handle supplied is not in the correct state.
The request cannot be made via a proxy.
12021 Registry Value Not Found
A required registry value could not be located.
A required registry value was located but is an incorrect type or has an invalid value.
Direct network access cannot be made at this time.
An asynchronous request could not be made because a zero context value was supplied.
An asynchronous request could not be made because a callback function has not been set.
The required operation could not be completed because one or more requests are pending.
The format of the request is invalid.
The requested item could not be located.
The attempt to connect to the server failed.
The connection with the server has been terminated.
The connection with the server has been reset.
Calls for the Win32 Internet function to redo the request.
The request to the proxy was invalid.
A user interface or other blocking operation has been requested.
This error code is not defined in WININET.
The request failed because the handle already exists.
SSL certificate date that was received from the server is bad. The certificate is expired.
SSL certificate common name (host name field) is incorrect.
The application is moving from a non-SSL (Secure Socket Layer) to an SSL connection because of a redirect.
The application is moving from an SSL (Secure Socket Layer) to a non-SSL connection because of a redirect.
Indicates that the content is not entirely secure. Some of the content being viewed may have come from unsecured servers.
The application is posting and attempting to change multiple lines of text on a server that is not secure.
The application is posting data to a server that is not secure.
An SSL protected resource on a Web server requires a valid client certificate.
A server SSL certificate was issued by an unknown or invalid certificate authority.
Client authorization is not setup up on this computer.
The application could not start an asynchronous thread.
The function could not handle the redirection, because the scheme changed (for example, HTTP to FTP).
Another thread has a password dialog box in progress.
The dialog box should be retried.
This error code is not defined in WININET.
12052 HTTPS to HTTP Submit Redir
The data being submitted to an SSL connection is being redirected to a non-SSL connection.
The request requires a CD-ROM to be inserted in the CD ROM drive to locate the resource requested.
The following are the error codes returned by the Internet API used to access FTP protocols.
The requested operation cannot be made on the FTP session handle because an operation is already in progress.
The FTP operation was not completed because the session was aborted.
Passive mode is not available on the server.
An error was detected while parsing data returned from the Gopher server.
The request must be made for a file locator.
An error was detected while receiving data from the Gopher server.
The end of the data has been reached.
The supplied locator is not valid.
The type of the locator is not correct for this operation.
The requested operation can only be made against a Gopher+ server or with a locator that specifies a Gopher+ operation.
The requested attribute could not be located.
The locator type is unknown.
The requested header could not be located.
The server did not return any headers.
The server response could not be parsed.
The supplied header is invalid.
The request made for HTTP Query Info is invalid.
The header could not be added because it already exists.
The redirection failed because either the scheme changed (for example, HTTP to FTP) or all attempts made to redirect failed (default is five attempts).
The application experienced an internal error loading the SSL libraries.
The function was unable to cache the file.
The required protocol stack is not loaded and the application cannot start WinSock.
The HTTP request was not redirected.
12161 Cookie Needs Confirmation
The HTTP cookie requires confirmation.
The HTTP cookie was declined by the server.
The Internet connection has been lost.
The Web site or server indicated is unreachable.
12165 Proxy Server Unreachable
The designated proxy server cannot be reached.
There was an error in the automatic proxy configuration script.
12167 Unable to Download Script
The automatic proxy configuration script could not be downloaded.
12168 Redirect Needs Confirmation
The redirection requires user confirmation.
SSL certificate is invalid.
SSL certificate was revoked.
12171 Failed Due to Security Check
The function failed due to a security check.