Description:
curl common return error code, the Chinese translation seems to be not very detailed, so the English version is posted below. Translate it again when you have time.
English:
CURLE_OK () _ is correct. As usual,
Curle _ Unsupported _ Protocol (1) _ The URL you sent to libcurl uses a protocol that is not supported by this libcurl. This may be caused by compile-time options that you didn't use (perhaps the protocol string is misspelled or the protocol libcurl code is not specified).
p>CURLE_FAILED_INIT (2) _ 2) _ very early initialization code failed. There may be an internal error or problem.
p>CURLE_URL_MALFORMAT (3) _ 3) _ URL format is incorrect.
curl _ couldnt _ resolve _ proxy (5) _ cannot resolve the proxy server. The specified proxy host cannot be resolved.
curl _ couldnt _ resolve _ host (6) _ cannot resolve the host. The specified remote host cannot be resolved.
p>CURLE_COULDNT_CONNECT (7) _ 7) _ cannot connect to the host or proxy server through connect ().
curl _ FTP _ weir _ server _ reply (8) _ after connecting to the FTP server, libcurl needs to receive a specific reply. This error code indicates that an abnormal or incorrect reply was received. The specified remote server may not be the correct FTP server.
curl _ remote _ access _ denied (9) _ we can't access the resource specified in the URL. For FTP, this happens if you try to change to a remote directory.
curl _ FTP _ weir _ pass _ reply (11) _ after sending the FTP password to the server, libcurl needs to receive a correct reply. This error code indicates that an unexpected code was returned.
curl _ FTP _ weir _ PASV _ reply (13) _ libcurl cannot receive useful results from the server as a response to the pasv or EPSV command. There is something wrong with the server.
curl _ FTP _ weir _ 227 _ format (14) _ FTP server returns 227 lines as a response to the PASV command. If libcurl cannot parse this row, it will return this code.
curl _ FTP _ cant _ get _ host (15) _ An internal error occurred while looking up the host for the new connection.
curl _ FTP _ couldnt _ set _ type (17) _ An error occurred while trying to set the transmission mode to binary or ascii.
p>CURLE_PARTIAL_FILE (18) _ 18) _ file transfer size is smaller or larger than expected. This error occurs when the server first reports an expected transmission size, and then the transmitted data does not match the previously specified size.
Curle _ FTP _ couldnt _ retr _ file (19) _' retr' command received an abnormal reply, or the completed transmission size was zero bytes.
curl _ QUOTE _ error (21) _ When sending a custom "quote" command to a remote server, one of the commands returned an error code of 4 or more (for FTP), or otherwise indicated that the command could not be completed successfully.
curl _ HTTP _ returned _ error (22) _ if CURLOPT_FAILONERROR is set to TRUE and the http server returns >; = 4, this code will be returned. (This error code was previously called curl _ http _ not _ found. )
curl _ write _ error (23) _ An error occurred while writing the received data to the local file, or an error was returned to libcurl by the write callback.
p>CURLE_UPLOAD_FAILED (25) _ 25) _ unable to start uploading. For FTP, the server usually refuses to execute the STOR command. The error buffer usually provides the server's explanation of this problem. (This error code was previously called curl _ FTP _ couldnt _ Stor _ file. )
curl _ read _ error (26) _ There was a problem reading the local file, or an error was returned by the read callback.
curl _ out _ of _ memory (27) _ memory allocation request failed. This error is serious. If this error occurs, it indicates that there is a very serious problem.
curl _ operation _ timed out (28) _ operation timed out. The timeout specified according to the situation has been reached. Please note: Since 6.6..2, the timeout period can be changed by itself. To specify the timeout of remote log download, open the urchin.conf file and uncomment the following line: DownloadTimeout: 3 Curle _ FTP _ Port _ Failed (3) _ FTP Port command returned an error. This problem is most likely to occur when an appropriate address is not specified for libcurl. See CURLOPT_FTPPORT.
the curl _ FTP _ couldnt _ use _ rest (31) _ FTP rest command returned an error. If the server is normal, this should not happen.
curl _ range _ error (33) _ The server does not support or accept the range request.
curl _ http _ post _ error (34) _ This problem is rare and is mainly caused by internal chaos.
curl _ SSL _ connect _ error (35) _ This error may occur when SSL/TLS is used at the same time. You can visit the error buffer to see the corresponding information, which will introduce this problem in more detail. This problem may be caused by certificates (file format, path, license), passwords and other factors.
curl _ FTP _ bad _ download _ resume (36) _ attempt to restore an FTP connection that exceeds the file size limit.
curl _ file _ couldnt _ read _ file (37) _ cannot open the file under the FILE:// path. The most likely reason is that the file path does not recognize the existing file. It is recommended that you check the access rights of files.
curl _ LDAP _ cannot _ bind (38) _ LDAP cannot be bound. The LDAP bind operation failed.
curl _ LDAP _ search _ failed (39) _ LDAP search failed.
curl _ function _ not _ found (41) _ function not found. The required zlib function could not be found.
curl _ aborted _ by _ callback (42) _ aborted by callback. The callback returned "abort" to libcurl.
curl _ bad _ function _ argument (43) _ internal error. The function was called with incorrect parameters.
p>CURLE_INTERFACE_FAILED (45) _ 45) _ interface error. The specified external interface cannot be used. Please set which interface to use to handle the source IP address of external connection through CURLOPT_INTERFACE. (This error code was previously called curl _ http _ port _ failed. )
curl _ too _ many _ redirects (47) _ too many redirects. When redirecting, libcurl reached the page click limit. Please use CURLOPT_MAXREDIRS to set the upper limit.
curl _ unknown _ telnet _ option (48) _ the option set with CURLOPT_TELNETOPTIONS is not recognized. Please refer to the related documents.
curl _ telnet _ option _ syntax (49) _ telnet option string is not in the correct format.
curl _ peer _ failed _ verification (51) _ the SSL certificate or SSH md5 fingerprint of the remote server is incorrect.
curl _ got _ nothing (52) _ The server did not return any data. In the corresponding case, failure to return any data is an error.
curl _ SSL _ engine _ notfound (53) _ the specified encryption engine cannot be found.
curl _ SSL _ engine _ set failed (54) _ the selected SSL encryption engine cannot be set as the default option.
curl _ send _ error (55) _ unable to send network data.
curl _ recv _ error (56) _ failed to receive network data.
p>CURLE_SSL_CERTPROBLEM (58) _ 58) _ There is a problem with the local client certificate
curl _ SSL _ cipher (59) _ The specified key
curl _ SSL _ cacert (6) cannot be used. _ unable to verify peer certifiCAte with known ca certificate
curl _ bad _ content _ encoding (61) _ unrecognized transmission encoding
curl _ LDAP _ invalid _ URL (62) _ invalid LDAP URL
curl _ filesize _ exceeded (63). _ file size limit exceeded
curl _ use _ SSL _ failed (64) _ FTP SSL level requested failed
curl _ send _ fail _ rewind (65) _ When sending, curl must rotate data for retransmission. But the slewing operation failed
curl _ SSL _ engine _ init failed (66) _ SSL engine initialization failed
curl _ login _ denied (67) _ remote server refused curl login (7.13.1 new function)
curl _ TFTP _ notfound (68). _ file
curl _ TFTP _ perm (69) not found on TFTP server _ permission problem encountered on TFTP server
curl _ remote _ disk _ full (7) _ server disk space is insufficient
curl _ TFTP _ illegal (71). _ TFTP operation is illegal
curl _ TFTP _ unknown ID (72) _ TFTP transmission ID unknown
curl _ remote _ file _ exists (73) _ file already exists. Unable to overwrite
p>CURLE_TFTP_NOSUCHUSER (74) _ 74) _ Normal TFTP server will not return this error
curl _ conv _ failed (75) _ character conversion failed
curl _ conv _ requd (76). _ the caller must register the conversion callback
curl _ SSL _ cacert _ badfile (77) _ There is a problem (possibly a path error or an access right problem) when reading the SSL CA certificate
curl _ remote _ file _ not _ found (78). _ the resource referenced in the URL does not exist
p>CURLE_SSH (79) _ SSH An unrecognized error occurred in the ssh session
curl _ SSL _ shutdown _ failed (8). _ unable to terminate SSL connection English:
almost "easy" interface functions return a curl code error code. no matter what, using the curl_easy_setopt option CURLOPT_ERRORBUFFER is a good idea as it will give you a human readable error string that may offer more details abo ut the cause of the error than just the error code. curl_easy_strerror can be called to get an error string f