The URL you passed uses an unsupported protocol. The problem might be an unused compile-time option or a misspelled protocol string.

Very early initialization code failed. This is likely an internal error or problem.

The URL was not properly formatted.

Not used.

The given proxy host could not be resolved.

The given remote host was not resolved.

Failed to connect to host or proxy.

After connecting to an FTP server, the IDLnetURL object received a strange or bad reply. The remote server is probably not an OK FTP server.

A service was denied by the FTP server due to lack of access. When a login fails, this is not returned.

This is never returned.

After sending the FTP password to the server, an unexpected code was received.

After sending a user name to the FTP server, an unexpected code was received.

The IDLnetURL object did not receive a sensible result from the server in response to either a PASV or EPSV command.

FTP servers return a 227-line as a response to a PASV command. This code is returned if the IDLnetURL object fails to parse that line.

Indicates an internal failure when looking up the host used for the new connection.

A bad return code for either the PASV or EPSV command was sent by the FTP server, preventing the IDLnetURL object from continuing.

An error was received when trying to set the transfer mode to binary.

A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously-given size.

Either the server returned a weird reply to a RETR command, or a zero-byte transfer was completed.

After a completed file transfer, the FTP server did not send a proper "transfer successful" code.

When sending custom QUOTE commands to the remote server, one of the commands returned an error code of 400 or higher.

This is returned if CURLOPT_FAILONERROR is TRUE and the HTTP server returns an error code that is >= 400.

An error occurred when writing received data to a local file, or an error was returned from a write callback.

Not used

The server denied the STOR operation. The error buffer usually contains the server's explanation.

There was a problem reading a local file, or the read callback returned an error.

A memory allocation request failed. This is not a good thing.

The specified time-out period was exceeded.

Failed to set ASCII transfer type (TYPE A).

The FTP PORT command returned an error. This often happens when the address is improper.

The FTP REST command failed.

The FTP SIZE command failed. SIZE is not a fundamental FTP command; it is an extension and not all servers support it. This is not a surprising error.

The HTTP server does not support or accept range requests.

This is an odd error that mainly occurs due to internal confusion.

A problem occurred somewhere in the SSL/TLS handshake. Check the error buffer for more information.

An FTP resume was attempted beyond the file size.

A file in the format of "FILE://" couldn't be opened, most likely because the file path is invalid. File permissions may also be the culprit.

The LDAP bind operation failed.

LDAP search failed.

The LDAP library was not found.

A required LDAP function was not found.

A callback returned an abort code.

Internal error. A function was called with a bad parameter.

Not used.

A specified outgoing interface could not be used. Use CURLOPT_INTERFACE to set the interface for outgoing connections.

Not used.

Too many redirects. When following redirects, IDL hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.

An option set with CURLOPT_TELNETOPTIONS was not recognized.

A TELNET option string was malformed.

Not used.

The remote server's SSL certificate is invalid.

The server returned nothing. In certain circumstances, getting nothing is considered an error.

The specified crypto engine wasn't found.

Can not set the selected SSL crypto engine as the default.

Sending network data failed.

Failure in receiving network data.

Share is in use.

There is a problem with the local certificate.

Could not use the specified cipher.

The peer certificate cannot be authenticated with known CA certificates.

Unrecognized transfer encoding.

Invalid LDAP URL.

Maximum file size exceeded.

Requested FTP SSL level failed.

Sending the data required rewinding the data to retransmit, but the rewind operation failed.

Failed to initialize the SSL engine.

The user password (or similar) was not accepted and the login failed.

File not found on TFTP server.

There is a permission problem on the TFTP server.

TFTP server is out of disk space.

Illegal TFTP operation.

Unknown TFTP transfer ID.

TFTP file already exists.

No such TFTP user.