Newer
Older
.\" You can view this file with:
.\" nroff -man [file]
.\" $Id$
.\"
.TH libcurl-errors 3 "9 Feb 2005" "libcurl 7.13.1" "libcurl errors"
libcurl-errors \- error codes in libcurl
.SH 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 problem.
.SH "CURLcode"
Almost all "easy" interface functions return a CURLcode error code. No matter
what, using the \fIcurl_easy_setopt(3)\fP option \fICURLOPT_ERRORBUFFER\fP 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. \fIcurl_easy_strerror(3)\fP can be called to get an error string from a
given CURLcode number.
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.
Very early initialization code failed. This is likely to be an internal error
or problem.
URL user malformatted. The user-part of the URL syntax was not correct.
Couldn't resolve proxy. The given proxy host could not be resolved.
Couldn't resolve host. The given remote host was not resolved.
After connecting to an FTP server, libcurl expects to get a certain 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.
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.
.IP "CURLE_FTP_USER_PASSWORD_INCORRECT (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.
After having sent the FTP password to the server, libcurl expects a proper
reply. This error code indicates that an unexpected code was returned.
After having sent user name to the FTP server, libcurl expects a proper
reply. This error code indicates that an unexpected code was returned.
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.
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.
An internal failure to lookup the host used for the new connection.
A bad return code on either PASV or EPSV was sent by the FTP server,
preventing libcurl from being able to continue.
Received an error when trying to set the transfer mode to binary.
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.
This was either a weird reply to a 'RETR' command or a zero byte transfer
complete.
After a completed file transfer, the FTP server did not respond a proper
\"transfer successful\" code.
When sending custom "QUOTE" commands to the remote server, one of the commands
returned an error code that was 400 or higher.
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP server
returns an error code that is >= 400.
An error occurred when writing received data to a local file, or an error was
returned to libcurl from a write callback.
Malformat user. User name badly specified. *Not currently used*
FTP couldn't STOR file. The server denied the STOR operation. The error buffer
usually contains the server's explanation to this.
There was a problem reading a local file or an error returned by the read
callback.
Out of memory. A memory allocation request failed. This is serious badness and
things are severely screwed up if this ever occur.
Operation timeout. The specified time-out period was reached according to the
conditions.
libcurl failed to set ASCII transfer type (TYPE A).
The FTP PORT command returned error. This mostly happen when you haven't
specified a good enough address for libcurl to use. See \fICURLOPT_FTPPORT\fP.
The FTP REST command returned error. This should never happen if the server is
sane.
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.
The HTTP server does not support or accept range requests.
This is an odd error that mainly occurs due to internal confusion.
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.
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?
Library not found. The LDAP library was not found.
Function not found. A required LDAP function was not found.
Aborted by callback. A callback returned "abort" to libcurl.
Internal error. A function was called with a bad parameter.
Internal error. A function was called in a bad order.
Interface error. A specified outgoing interface could not be used. Set which
interface to use for outgoing connections' source IP address with
CURLOPT_INTERFACE.
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.
Too many redirects. When following redirects, libcurl hit the maximum amount.
Set your limit with CURLOPT_MAXREDIRS.
An option set with CURLOPT_TELNETOPTIONS was not recognized/known. Refer to
the appropriate documentation.
A telnet option string was Illegally formatted.
This is not an error. This used to be another error code in an old libcurl
version and is currently unused.
The remote server's SSL certificate was deemed not OK.
Nothing was returned from the server, and under the circumstances, getting
nothing is considered an error.
Failed setting the selected SSL crypto engine as default!
.IP "CURLE_SHARE_IN_USE (57)"
Share is in use
problem with the local client certificate
problem with the CA cert (path? access rights?)
.IP "CURLE_FTP_SSL_FAILED (64)"
Requested FTP SSL level failed
.IP "CURLE_SEND_FAIL_REWIND (65)"
When doing a send operation curl had to rewind the data to retransmit, but the
rewinding operation failed
.IP "CURLE_SSL_ENGINE_INITFAILED (66)"
Initiating the SSL Engine failed
.IP "CURLE_LOGIN_DENIED (67)"
The remote server denied curl to login (Added in 7.13.1)
.SH "CURLMcode"
This is the generic return code used by functions in the libcurl multi
.IP "CURLM_CALL_MULTI_PERFORM (-1)"
This is not really an error. It means you should call
\fIcurl_multi_perform(3)\fP again without doing select() or similar in between.
.IP "CURLM_OK (0)"
Things are fine.
.IP "CURLM_BAD_HANDLE (1)"
The passed-in handle is not a valid CURLM handle.
.IP "CURLM_BAD_EASY_HANDLE (2)"
An easy handle was not good/valid.
.IP "CURLM_OUT_OF_MEMORY (3)"
You are doomed.
.IP "CURLM_INTERNAL_ERROR (4)"
This can only be returned if libcurl bugs. Please report it to us!
.IP "CURLM_BAD_SOCKET (5)"
The passed-in socket is not a valid one that libcurl already knows about.
(Added in 7.16.0)
.SH "CURLSHcode"
The "share" interface will return a CURLSHcode to indicate when an error has
.IP "CURLSHE_OK (0)"
All fine. Proceed as usual.
.IP "CURLSHE_BAD_OPTION (1)"
An invalid option was passed to the function.
.IP "CURLSHE_IN_USE (2)"
The share object is currently in use.
.IP "CURLSHE_INVALID (3)"
An invalid share object was passed to the function.