2024年4月27日发(作者：)
libcurl-errors(3) libcurlerrors libcurl-errors(3)
NAME
libcurl-errors − error codes in libcurl
DESCRIPTION
This man page includes most, if not all, available error codes in yoccur and possibly what
you can do to fix the problem are also included.
CURLcode
Almost all "easy" interface functions return a CURLcode error code. No matter what, using the
curl_easy_setopt(3)optionCURLOPT_ERRORBUFFERis a good idea as it will give you a human read-
able error string that may offer more details about the cause of the error than just the error code.
curl_easy_strerror(3)can be called to get an error string from a givenCURLcode number.
CURLcode is one of the following:
CURLE_OK (0)
All fine. Proceed as usual.
CURLE_UNSUPPORTED_PROT OCOL (1)
The URL you passed to libcurl used a protocol that this libcurl does not support. The support
might be a compile-time option that you didn’tuse, it can be a misspelled protocol string or just a
protocol libcurl has no code for.
CURLE_FAILED_INIT (2)
Very early initialization code failed. This is likely to be an internal error or problem.
CURLE_URL_MALFORMAT(3)
The URL was not properly formatted.
CURLE_COULDNT_RESOLVE_PROXY(5)
Couldn’ givenproxy host could not be resolved.
CURLE_COULDNT_RESOLVE_HOST (6)
Couldn’tresolvehost. The givenremote host was not resolved.
CURLE_COULDNT_CONNECT (7)
Failed to connect() to host or proxy.
CURLE_FTP_WEIRD_SERVER_REPLY(8)
After connecting to a FTP server,libcurl expects to get a certain reply back. This error code
implies that it got a strange or bad givenremote server is probably not an OK FTP
server.
CURLE_REMOTE_ACCESS_DENIED (9)
We were denied access to the resource giveninthe ,this occurs while trying to
change to the remote directory.
CURLE_FTP_WEIRD_PASS_REPLY(11)
After having sent the FTP password to the server,libcurl expects a proper error code
indicates that an unexpected code was returned.
CURLE_FTP_WEIRD_PASV_REPLY(13)
libcurl failed to get a sensible result back from the server as a response to either a PASV or a
EPSV command. The server is flawed.
CURLE_FTP_WEIRD_227_FORMAT(14)
FTP servers return a 227-line as a response to a PASV command. If libcurl fails to parse that line,
this return code is passed back.
CURLE_FTP_CANT_GET_HOST (15)
An internal failure to lookup the host used for the newconnection.
libcurl 7.19.08Jun 20081
libcurl-errors(3) libcurlerrors libcurl-errors(3)
CURLE_FTP_COULDNT_SET_TYPE (17)
Receivedanerror when trying to set the transfer mode to binary or ASCII.
CURLE_PARTIAL_FILE (18)
Afile transfer was shorter or larger than expected. This happens when the server first reports an
expected transfer size, and then delivers data that doesn’tmatch the previously givensize.
CURLE_FTP_COULDNT_RETR_FILE (19)
This was either a weird reply to a ’RETR’ command or a zero byte transfer complete.
CURLE_QUOTE_ERROR (21)
When sending custom "QUOTE" commands to the remote server,one of the commands returned
an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of
the command.
CURLE_HTTP_RETURNED_ERROR (22)
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error
code that is >= 400. (This error code was formerly known as CURLE_HTTP_NOT_FOUND.)
CURLE_WRITE_ERROR (23)
An error occurred when writing receiveddata to a local file, or an error was returned to libcurl
from a write callback.
CURLE_UPLOAD_FAILED (25)
Failed starting the upload. For FTP,the server typically denied the STOR command. The error
buffer usually contains the server’sexplanation for this.(This error code was formerly known as
CURLE_FTP_COULDNT_STOR_FILE.)
CURLE_READ_ERROR (26)
There was a problem reading a local file or an error returned by the read callback.
CURLE_OUT_OF_MEMORY(27)
Amemory allocation request failed. This is serious badness and things are severely screwed up if
this everoccurs.
CURLE_OPERATION_TIMEDOUT (28)
Operation timeout. The specified time-out period was reached according to the conditions.
CURLE_FTP_PORT_FAILED (30)
The FTP PORTcommand returned mostly happens when you haven’tspecified a good
enough address for libcurl to use. SeeCURLOPT_FTPPORT.
CURLE_FTP_COULDNT_USE_REST (31)
The FTP REST command returned should neverhappen if the server is sane.
CURLE_RANGE_ERROR (33)
The server does not support or accept range requests.
CURLE_HTTP_POST_ERROR (34)
This is an odd error that mainly occurs due to internal confusion.
CURLE_SSL_CONNECT_ERROR (35)
Aproblem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and
read the message there as it pinpoints the problem slightly more. Could be certificates (file for-
mats, paths, permissions), passwords, and others.
CURLE_FTP_BAD_DOWNLOAD_RESUME (36)
Attempting FTP resume beyond file size.
CURLE_FILE_COULDNT_READ_FILE (37)
Afile givenwith FILE:// couldn’tbeopened. Most likely because the file path doesn’tidentify an
existing file. Did you check file permissions?
libcurl 7.19.08Jun 20082
libcurl-errors(3) libcurlerrors libcurl-errors(3)
CURLE_LDAP_CANNOT_BIND (38)
LDAP cannot bind. LDAP bind operation failed.
CURLE_LDAP_SEARCH_FAILED (39)
LDAP search failed.
CURLE_FUNCTION_NOT_FOUND (41)
Function not found. A required zlib function was not found.
CURLE_ABORTED_BY_CALLBACK(42)
Aborted by callback. A callback returned "abort" to libcurl.
CURLE_BAD_FUNCTION_ARGUMENT (43)
Internal ion was called with a bad parameter.
CURLE_INTERFACE_FAILED (45)
Interface fied outgoing interface could not be used. Set which interface to use for
outgoing connections’ source IP address with CURLOPT_INTERFACE. (This error code was for-
merly known as CURLE_HTTP_PORT_FAILED.)
CURLE_TOO_MANY_REDIRECTS (47)
Toomanyredirects. When following redirects, libcurl hit the maximum your limit
with CURLOPT_MAXREDIRS.
CURLE_UNKNOWN_TELNET_OPTION (48)
An option set with CURLOPT_TELNETOPTIONS was not recognized/known. Refer to the
appropriate documentation.
CURLE_TELNET_OPTION_SYNTAX (49)
Atelnet option string was Illegally formatted.
CURLE_PEER_FAILED_VERIFICATION (51)
The remote server’sSSL certificate or SSH md5 fingerprint was deemed not OK.
CURLE_GOT_NOTHING (52)
Nothing was returned from the server,and under the circumstances, getting nothing is considered
an error.
CURLE_SSL_ENGINE_NOTFOUND (53)
The specified crypto engine wasn’tfound.
CURLE_SSL_ENGINE_SETFAILED (54)
Failed setting the selected SSL crypto engine as default!
CURLE_SEND_ERROR (55)
Failed sending network data.
CURLE_RECV_ERROR (56)
Failure with receiving network data.
CURLE_SSL_CERTPROBLEM (58)
problem with the local client certificate.
CURLE_SSL_CIPHER (59)
Couldn’tuse specified cipher.
CURLE_SSL_CACERT(60)
Peer certificate cannot be authenticated with known CA certificates.
CURLE_BAD_CONTENT_ENCODING (61)
Unrecognized transfer encoding.
CURLE_LDAP_INVALID_URL (62)
Invalid LDAP URL.
libcurl 7.19.08Jun 20083
libcurl-errors(3) libcurlerrors libcurl-errors(3)
CURLE_FILESIZE_EXCEEDED (63)
Maximum file size exceeded.
CURLE_USE_SSL_FAILED (64)
Requested FTP SSL levelfailed.
CURLE_SEND_FAIL_REWIND (65)
When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation
failed.
CURLE_SSL_ENGINE_INITFAILED (66)
Initiating the SSL Engine failed.
CURLE_LOGIN_DENIED (67)
The remote server denied curl to login (Added in 7.13.1)
CURLE_TFTP_NOTFOUND (68)
File not found on TFTP server.
CURLE_TFTP_PERM (69)
Permission problem on TFTP server.
CURLE_REMOTE_DISK_FULL (70)
Out of disk space on the server.
CURLE_TFTP_ILLEGAL (71)
IllegalTFTP operation.
CURLE_TFTP_UNKNOWNID (72)
Unknown TFTP transfer ID.
CURLE_REMOTE_FILE_EXISTS (73)
File already exists and will not be overwritten.
CURLE_TFTP_NOSUCHUSER (74)
This error should neverbereturned by a properly functioning TFTP server.
CURLE_CONV_FAILED (75)
Character conversion failed.
CURLE_CONV_REQD (76)
Caller must register conversion callbacks.
CURLE_SSL_CACERT_BADFILE (77)
Problem with reading the SSL CA cert (path? access rights?)
CURLE_REMOTE_FILE_NOT_FOUND (78)
The resource referenced in the URL does not exist.
CURLE_SSH (79)
An unspecified error occurred during the SSH session.
CURLE_SSL_SHUTDOWN_FAILED (80)
Failed to shut down the SSL connection.
CURLE_AGAIN (81)
Socket is not ready for send/recv wait till it’sready and try again. This return code is only returned
fromcurl_easy_recv(3)andcurl_easy_send(3)(Added in 7.18.2)
CURLE_SSL_CRL_BADFILE (82)
Failed to load CRL file (Added in 7.19.0)
CURLE_SSL_ISSUER_ERROR (83)
Issuer check failed (Added in 7.19.0)
libcurl 7.19.08Jun 20084
libcurl-errors(3) libcurlerrors libcurl-errors(3)
CURLE_OBSOLETE*
These error codes will neverbereturned. Theywere used in an old libcurl version and are cur-
rently unused.
CURLMcode
This is the generic return code used by functions in the libcurl multi interface. Also consider
curl_multi_strerror(3).
CURLM_CALL_MULTI_PERFORM (-1)
This is not really an s you should callcurl_multi_perform(3)again without doing
select() or similar in between.
CURLM_OK (0)
Things are fine.
CURLM_BAD_HANDLE (1)
The passed-in handle is not a valid CURLM handle.
CURLM_BAD_EASY_HANDLE (2)
An easy handle was not good/valid. It could mean that it isn’taneasy handle at all, or possibly that
the handle already is in used by this or another multi handle.
CURLM_OUT_OF_MEMORY(3)
Youare doomed.
CURLM_INTERNAL_ERROR (4)
This can only be returned if libcurl bugs. Please report it to us!
CURLM_BAD_SOCKET (5)
The passed-in socket is not a valid one that libcurl already knows about.(Added in 7.15.4)
CURLM_UNKNOWN_OPTION (6)
curl_multi_setopt() with unsupported option (Added in 7.15.4)
CURLSHcode
The "share" interface will return a CURLSHcode to indicate when an error has consider
curl_share_strerror(3).
CURLSHE_OK (0)
All fine. Proceed as usual.
CURLSHE_BAD_OPTION (1)
An invalid option was passed to the function.
CURLSHE_IN_USE (2)
The share object is currently in use.
CURLSHE_INVALID (3)
An invalid share object was passed to the function.
CURLSHE_NOMEM (4)
Not enough memory was available. (Addedin 7.12.0)
libcurl 7.19.08Jun 20085
发布评论