2023年6月25日发(作者：)

CURL错误代码及含义（英⽂）NAMElibcurl-errors - error codes in libcurlDESCRIPTIONThis man page includes most, if not all, available error codes in libcurl. Why they occur and possibly what you can do to fix theproblem are also deAlmost all "easy" interface functions return a CURLcode error code. No matter what, usingthecurl_easy_setopt(3)optionCURLOPT_ERRORBUFFERis a good idea as it will give you a human readable error string that mayoffer more details about the cause of the error than just the error _easy_strerror(3)can be called to get an errorstring from a given CURLcode de is one of the following:CURLE_OK (0)All fine. Proceed as _UNSUPPORTED_PROTOCOL (1)The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time optionthat you didn't use, it can be a misspelled protocol string or just a protocol libcurl has no code _FAILED_INIT (2)Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where somethingfundamental couldn't get done at init _URL_MALFORMAT (3)The URL was not properly _NOT_BUILT_IN (4)A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that afeature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to geta rebuilt _COULDNT_RESOLVE_PROXY (5)Couldn't resolve proxy. The given proxy host could not be _COULDNT_RESOLVE_HOST (6)Couldn't resolve host. The given remote host was not _COULDNT_CONNECT (7)Failed to connect() to host or _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 orbad reply. The given remote server is probably not an OK FTP _REMOTE_ACCESS_DENIED (9)We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote _FTP_WEIRD_PASS_REPLY (11)After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpectedcode was _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 _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 _FTP_PRET_FAILED (84)The FTP server does not understand the PRET command at all or does not support the given argument. Be careful whenusingCURLOPT_CUSTOMREQUEST, a custom LIST command will be sent with PRET CMD before PASV as well. (Added in7.20.0)CURLE_FTP_CANT_GET_HOST (15)An internal failure to lookup the host used for the new _FTP_COULDNT_SET_TYPE (17)Received an error when trying to set the transfer mode to binary or _PARTIAL_FILE (18)A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, andthen delivers data that doesn't match the previously given _FTP_COULDNT_RETR_FILE (19)This was either a weird reply to a 'RETR' command or a zero byte transfer _QUOTE_ERROR (21)When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400or higher (for FTP) or otherwise indicated unsuccessful completion of the _HTTP_RETURNED_ERROR (22)This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server returns an error code that is >= _WRITE_ERROR (23)An error occurred when writing received data to a local file, or an error was returned to libcurl from a write _UPLOAD_FAILED (25)Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains theserver's explanation for _READ_ERROR (26)There was a problem reading a local file or an error returned by the read _OUT_OF_MEMORY (27)A memory allocation request failed. This is serious badness and things are severely screwed up if this ever _OPERATION_TIMEDOUT (28)Operation timeout. The specified time-out period was reached according to the _FTP_PORT_FAILED (30)The FTP PORT command returned error. This mostly happens when you haven't specified a good enough address for libcurl touse. SeeCURLOPT__FTP_COULDNT_USE_REST (31)The FTP REST command returned error. This should never happen if the server is _RANGE_ERROR (33)The server does not support or accept range _HTTP_POST_ERROR (34)This is an odd error that mainly occurs due to internal _SSL_CONNECT_ERROR (35)A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as itpinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and _BAD_DOWNLOAD_RESUME (36)The download could not be resumed because the specified offset was out of the file _FILE_COULDNT_READ_FILE (37)A file given with FILE:// couldn't be opened. Most likely because the file path doesn't identify an existing file. Did you check filepermissions?CURLE_LDAP_CANNOT_BIND (38)LDAP cannot bind. LDAP bind operation _LDAP_SEARCH_FAILED (39)LDAP search _FUNCTION_NOT_FOUND (41)Function not found. A required zlib function was not _ABORTED_BY_CALLBACK (42)Aborted by callback. A callback returned "abort" to _BAD_FUNCTION_ARGUMENT (43)Internal error. A function was called with a bad _INTERFACE_FAILED (45)Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections' sourceIP address with CURLOPT__TOO_MANY_REDIRECTS (47)Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPT__UNKNOWN_OPTION (48)An option passed to libcurl is not recognized/known. Refer to the appropriate documentation. This is most likely a problem inthe program that uses libcurl. The error buffer might contain more specific information about which exact option it _TELNET_OPTION_SYNTAX (49)A telnet option string was Illegally _PEER_FAILED_VERIFICATION (51)The remote server's SSL certificate or SSH md5 fingerprint was deemed not _GOT_NOTHING (52)Nothing was returned from the server, and under the circumstances, getting nothing is considered an _SSL_ENGINE_NOTFOUND (53)The specified crypto engine wasn't _SSL_ENGINE_SETFAILED (54)Failed setting the selected SSL crypto engine as default!CURLE_SEND_ERROR (55)Failed sending network _RECV_ERROR (56)Failure with receiving network _SSL_CERTPROBLEM (58)problem with the local client _SSL_CIPHER (59)Couldn't use specified _SSL_CACERT (60)Peer certificate cannot be authenticated with known CA _BAD_CONTENT_ENCODING (61)Unrecognized transfer _LDAP_INVALID_URL (62)Invalid LDAP _FILESIZE_EXCEEDED (63)Maximum file size _USE_SSL_FAILED (64)Requested FTP SSL level _SEND_FAIL_REWIND (65)When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation _SSL_ENGINE_INITFAILED (66)Initiating the SSL Engine _LOGIN_DENIED (67)The remote server denied curl to login (Added in 7.13.1)CURLE_TFTP_NOTFOUND (68)File not found on TFTP _TFTP_PERM (69)Permission problem on TFTP _REMOTE_DISK_FULL (70)Out of disk space on the _TFTP_ILLEGAL (71)Illegal TFTP _TFTP_UNKNOWNID (72)Unknown TFTP transfer _REMOTE_FILE_EXISTS (73)File already exists and will not be _TFTP_NOSUCHUSER (74)This error should never be returned by a properly functioning TFTP _CONV_FAILED (75)Character conversion _CONV_REQD (76)Caller must register conversion _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 _SSH (79)An unspecified error occurred during the SSH _SSL_SHUTDOWN_FAILED (80)Failed to shut down the SSL _AGAIN (81)Socket is not ready for send/recv wait till it's ready and try again. This return code is only returnedfromcurl_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)CURLE_FTP_PRET_FAILED (84)PRET command failedCURLE_RTSP_CSEQ_ERROR (85)Mismatch of RTSP CSeq _RTSP_SESSION_ERROR (86)Mismatch of RTSP Session _FTP_BAD_FILE_LIST (87)Unable to parse FTP file list (during FTP wildcard downloading).CURLE_CHUNK_FAILED (88)Chunk callback reported _OBSOLETE*These error codes will never be returned. They were used in an old libcurl version and are currently odeThis is the generic return code used by functions in the libcurl multi interface. Also considercurl_multi_strerror(3).CURLM_CALL_MULTI_PERFORM (-1)This is not really an error. It means you should callcurl_multi_perform(3)again without doing select() or similar in _OK (0)Things are _BAD_HANDLE (1)The passed-in handle is not a valid CURLM _BAD_EASY_HANDLE (2)An easy handle was not good/valid. It could mean that it isn't an easy handle at all, or possibly that the handle already is inused by this or another multi _OUT_OF_MEMORY (3)You are _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)CURLSHcodeThe "share" interface will return a CURLSHcode to indicate when an error has occurred. Also considercurl_share_strerror(3).CURLSHE_OK (0)All fine. Proceed as E_BAD_OPTION (1)An invalid option was passed to the E_IN_USE (2)The share object is currently in E_INVALID (3)An invalid share object was passed to the E_NOMEM (4)Not enough memory was available. (Added in 7.12.0)