|
Code
|
Code Number
|
Description
|
|
1
|
The URL you passed uses an unsupported protocol. The problem might be an unused compile-time option or a misspelled protocol string.
|
|
2
|
Very early initialization code failed. This is likely an internal error or problem.
|
|
3
|
The URL was not properly formatted.
|
|
4
|
Not used.
|
|
5
|
The given proxy host could not be resolved.
|
|
6
|
The given remote host was not resolved.
|
|
7
|
Failed to connect to host or proxy.
|
|
8
|
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.
|
|
9
|
A service was denied by the FTP server due to lack of access. When a login fails, this is not returned.
|
|
10
|
This is never returned.
|
|
11
|
After sending the FTP password to the server, an unexpected code was received.
|
|
12
|
After sending a user name to the FTP server, an unexpected code was received.
|
|
13
|
The IDLnetURL object did not receive a sensible result from the server in response to either a PASV or EPSV command.
|
|
14
|
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.
|
|
15
|
Indicates an internal failure when looking up the host used for the new connection.
|
|
16
|
A bad return code for either the PASV or EPSV command was sent by the FTP server, preventing the IDLnetURL object from continuing.
|
|
17
|
An error was received when trying to set the transfer mode to binary.
|
|
18
|
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.
|
|
19
|
Either the server returned a weird reply to a RETR command, or a zero-byte transfer was completed.
|
|
20
|
After a completed file transfer, the FTP server did not send a proper "transfer successful" code.
|
|
21
|
When sending custom QUOTE commands to the remote server, one of the commands returned an error code of 400 or higher.
|
|
22
|
This is returned if CURLOPT_FAILONERROR is TRUE and the HTTP server returns an error code that is >= 400.
|
|
23
|
An error occurred when writing received data to a local file, or an error was returned from a write callback.
|
|
24
|
Not used
|
|
25
|
The server denied the STOR operation. The error buffer usually contains the server's explanation.
|
|
26
|
There was a problem reading a local file, or the read callback returned an error.
|
|
27
|
A memory allocation request failed. This is not a good thing.
|
|
28
|
The specified time-out period was exceeded.
|
|
29
|
Failed to set ASCII transfer type (TYPE A).
|
|
30
|
The FTP PORT command returned an error. This often happens when the address is improper.
|
|
31
|
The FTP REST command failed.
|
|
32
|
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.
|
|
33
|
The HTTP server does not support or accept range requests.
|
|
34
|
This is an odd error that mainly occurs due to internal confusion.
|
|
35
|
A problem occurred somewhere in the SSL/TLS handshake. Check the error buffer for more information.
|
|
36
|
An FTP resume was attempted beyond the file size.
|
|
37
|
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.
|
|
38
|
The LDAP bind operation failed.
|
|
39
|
LDAP search failed.
|
|
40
|
The LDAP library was not found.
|
|
41
|
A required LDAP function was not found.
|
|
42
|
A callback returned an abort code.
|
|
43
|
Internal error. A function was called with a bad parameter.
|
|
44
|
Not used.
|
|
45
|
A specified outgoing interface could not be used. Use CURLOPT_INTERFACE to set the interface for outgoing connections.
|
|
46
|
Not used.
|
|
47
|
Too many redirects. When following redirects, IDL hit the maximum amount. Set your limit with CURLOPT_MAXREDIRS.
|
|
48
|
An option set with CURLOPT_TELNETOPTIONS was not recognized.
|
|
49
|
A TELNET option string was malformed.
|
|
50
|
Not used.
|
|
51
|
The remote server's SSL certificate is invalid.
|
|
52
|
The server returned nothing. In certain circumstances, getting nothing is considered an error.
|
|
53
|
The specified crypto engine wasn't found.
|
|
54
|
Can not set the selected SSL crypto engine as the default.
|
|
55
|
Sending network data failed.
|
|
56
|
Failure in receiving network data.
|
|
57
|
Share is in use.
|
|
58
|
There is a problem with the local certificate.
|
|
59
|
Could not use the specified cipher.
|
|
60
|
The peer certificate cannot be authenticated with known CA certificates.
|
|
61
|
Unrecognized transfer encoding.
|
|
62
|
Invalid LDAP URL.
|
|
63
|
Maximum file size exceeded.
|
|
64
|
Requested FTP SSL level failed.
|
|
65
|
Sending the data required rewinding the data to retransmit, but the rewind operation failed.
|
|
66
|
Failed to initialize the SSL engine.
|
|
67
|
The user password (or similar) was not accepted and the login failed.
|
|
68
|
File not found on TFTP server.
|
|
69
|
There is a permission problem on the TFTP server.
|
|
70
|
TFTP server is out of disk space.
|
|
71
|
Illegal TFTP operation.
|
|
72
|
Unknown TFTP transfer ID.
|
|
73
|
TFTP file already exists.
|
|
74
|
No such TFTP user.
|
