Manual Pages for UNIX Darwin command on man libcurl-errors

libcurl-errors(3) libcurl errors libcurl-errors(3)

NAME

libcurl-errors - error codes in libcurl

DESCRIPTION

This man page includes most, if not all, available error codes in

libcurl. Why they occur and possibly what you can do to fix the prob-

lem. CCUURRLLccooddee Almost all "easy" interface functions return a CURLcode error code. No

matter what, using the curleasysetopt(3) option CURLOPTERRORBUFFER

is a good idea as it will give you a human readable error string that may offer more details about the error cause than just the error code does. curleasystrerror(3) can be called to get an error string from a given CURLcode number. CURLcode is one of the following: CURLEOK (0) All fine. Proceed as usual. CURLEUNSUPPORTEDPROTOCOL (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't use, it can be a misspelled protocol string or just a protocol libcurl has no code for. CURLEFAILEDINIT (2) Very early initialization code failed. This is likely to be an internal error or problem. CURLEURLMALFORMAT (3) The URL was not properly formatted. CURLEURLMALFORMATUSER (4)

URL user malformatted. The user-part of the URL syntax was not

correct. CURLECOULDNTRESOLVEPROXY (5) Couldn't resolve proxy. The given proxy host could not be resolved. CURLECOULDNTRESOLVEHOST (6) Couldn't resolve host. The given remote host was not resolved. CURLECOULDNTCONNECT (7) Failed to connect() to host or proxy. CURLEFTPWEIRDSERVERREPLY (8)

After connecting to an FTP server, libcurl expects to get a cer-

tain reply back. This error code implies that it god a strange or bad reply. The given remote server is probably not an OK FTP server. CURLEFTPACCESSDENIED (9) We were denied access when trying to login to an FTP server or when trying to change working directory to the one given in the URL. CURLEFTPUSERPASSWORDINCORRECT (10) The FTP server rejected access to the server after the password was sent to it. It might be because the username and/or the password were incorrect or just that the server is not allowing you access for the moment etc. CURLEFTPWEIRDPASSREPLY (11) After having sent the FTP password to the server, libcurl

expects a proper reply. This error code indicates that an unex-

pected code was returned. CURLEFTPWEIRDUSERREPLY (12) After having sent user name to the FTP server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned. CURLEFTPWEIRDPASVREPLY (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. CURLEFTPWEIRD227FORMAT (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. CURLEFTPCANTGETHOST (15)

An internal failure to lookup the host used for the new connec-

tion. CURLEFTPCANTRECONNECT (16) A bad return code on either PASV or EPSV was sent by the FTP server, preventing libcurl from being able to continue. CURLEFTPCOULDNTSETBINARY (17) Received an error when trying to set the transfer mode to binary. CURLEPARTIALFILE (18)

A file transfer was shorter or larger than expected. This hap-

pens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size. CURLEFTPCOULDNTRETRFILE (19) This was either a weird reply to a 'RETR' command or a zero byte transfer complete.

CURLEFTPWRITEERROR (20)

After a completed file transfer, the FTP server did not respond a proper

CURLEFTPQUOTEERROR (21)

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

CURLEHTTPRETURNEDERROR (22)

This is returned if CURLOPTFAILONERROR is set TRUE and the HTTP

server returns an error code that is >= 400.

CURLEWRITEERROR (23)

An error occurred when writing received data to a local file, or an error was returned to libcurl from a write callback. CURLEMALFORMATUSER (24) Malformat user. User name badly specified. *Not currently used* CURLEFTPCOULDNTSTORFILE (25) FTP couldn't STOR file. The server denied the STOR operation. The error buffer usually contains the server's explanation to this.

CURLEREADERROR (26)

There was a problem reading a local file or an error returned by the read callback. CURLEOUTOFMEMORY (27)

Out of memory. A memory allocation request failed. This is seri-

ous badness and things are severely screwed up if this ever occur. CURLEOPERATIONTIMEOUTED (28)

Operation timeout. The specified time-out period was reached

according to the conditions. CURLEFTPCOULDNTSETASCII (29) libcurl failed to set ASCII transfer type (TYPE A). CURLEFTPPORTFAILED (30) The FTP PORT command returned error. This mostly happen when you haven't specified a good enough address for libcurl to use. See CURLOPTFTPPORT. CURLEFTPCOULDNTUSEREST (31) The FTP REST command returned error. This should never happen if the server is sane. CURLEFTPCOULDNTGETSIZE (32) The FTP SIZE command returned error. SIZE is not a kosher FTP command, it is an extension and not all servers support it. This is not a surprising error.

CURLEHTTPRANGEERROR (33)

The HTTP server does not support or accept range requests.

CURLEHTTPPOSTERROR (34)

This is an odd error that mainly occurs due to internal confu-

sion.

CURLESSLCONNECTERROR (35)

A problem 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 formats, paths, permissions), passwords, and others. CURLEFTPBADDOWNLOADRESUME (36) Attempting FTP resume beyond file size. CURLEFILECOULDNTREADFILE (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 file permissions? CURLELDAPCANNOTBIND (38) LDAP cannot bind. LDAP bind operation failed. CURLELDAPSEARCHFAILED (39) LDAP search failed. CURLELIBRARYNOTFOUND (40) Library not found. The LDAP library was not found. CURLEFUNCTIONNOTFOUND (41) Function not found. A required LDAP function was not found. CURLEABORTEDBYCALLBACK (42) Aborted by callback. A callback returned "abort" to libcurl. CURLEBADFUNCTIONARGUMENT (43) Internal error. A function was called with a bad parameter. CURLEBADCALLINGORDER (44) Internal error. A function was called in a bad order. CURLEHTTPPORTFAILED (45) Interface error. A specified outgoing interface could not be used. Set which interface to use for outgoing connections' source IP address with CURLOPTINTERFACE. CURLEBADPASSWORDENTERED (46) Bad password entered. An error was signaled when the password was entered. This can also be the result of a "bad password" returned from a specified password callback. CURLETOOMANYREDIRECTS (47) Too many redirects. When following redirects, libcurl hit the maximum amount. Set your limit with CURLOPTMAXREDIRS.

CURLEUNKNOWNTELNETOPTION (48)

An option set with CURLOPTTELNETOPTIONS was not recog-

nized/known. Refer to the appropriate documentation.

CURLETELNETOPTIONSYNTAX (49)

A telnet option string was Illegally formatted. CURLEOBSOLETE (50) This is not an error. This used to be another error code in an old libcurl version and is currently unused. CURLESSLPEERCERTIFICATE (51) The remote server's SSL certificate was deemed not OK. CURLEGOTNOTHING (52)

Nothing was returned from the server, and under the circum-

stances, getting nothing is considered an error. CURLESSLENGINENOTFOUND (53) The specified crypto engine wasn't found. CURLESSLENGINESETFAILED (54) Failed setting the selected SSL crypto engine as default!

CURLESENDERROR (55)

Failed sending network data.

CURLERECVERROR (56)

Failure with receiving network data. CURLESHAREINUSE (57) Share is in use CURLESSLCERTPROBLEM (58) problem with the local client certificate CURLESSLCIPHER (59) couldn't use specified cipher CURLESSLCACERT (60) problem with the CA cert (path? access rights?) CURLEBADCONTENTENCODING (61) Unrecognized transfer encoding CURLELDAPINVALIDURL (62) Invalid LDAP URL CURLEFILESIZEEXCEEDED (63) Maximum file size exceeded CURLEFTPSSLFAILED (64) Requested FTP SSL level failed CURLESENDFAILREWIND (65) When doing a send operation curl had to rewind the data to retransmit, but the rewinding operation failed CURLESSLENGINEINITFAILED (66) Initiating the SSL Engine failed CURLELOGINDENIED (67) The remote server denied curl to login (Added in 7.13.1) CCUURRLLMMccooddee This is the generic return code used by functions in the libcurl multi interface. Also consider curlmultistrerror(3).

CURLMCALLMULTIPERFORM (-1)

This is not really an error. It means you should call curlmultiperform(3) again without doing select() or similar in between. CURLMOK (0) Things are fine. CURLMBADHANDLE (1)

The passed-in handle is not a valid CURLM handle.

CURLMBADEASYHANDLE (2) An easy handle was not good/valid. CURLMOUTOFMEMORY (3) You are doomed.

CURLMINTERNALERROR (4)

This can only be returned if libcurl bugs. Please report it to us! CCUURRLLSSHHccooddee The "share" interface will return a CURLSHcode to indicate when an error has occurred. Also consider curlsharestrerror(3). CURLSHcode is one of the following: CURLSHEOK (0) All fine. Proceed as usual.

CURLSHEBADOPTION (1)

An invalid option was passed to the function. CURLSHEINUSE (2) The share object is currently in use. CURLSHEINVALID (3) An invalid share object was passed to the function.