Lines Matching full:libcurl
23 .TH libcurl-errors 3 "August 22, 2016" "libcurl 7.58.0" "libcurl errors"
26 libcurl-errors \- error codes in libcurl
28 This man page includes most, if not all, available error codes in libcurl.
42 The URL you passed to libcurl used a protocol that this libcurl does not
44 can be a misspelled protocol string or just a protocol libcurl has no code
53 A requested feature, protocol or option was not found built-in in this libcurl
55 enabled or explicitly disabled when libcurl was built and in order to get it
56 to function you have to get a rebuilt libcurl.
64 The server sent data libcurl couldn't parse. This error code is used for more
73 After having sent the FTP password to the server, libcurl expects a proper
79 libcurl failed to get a sensible result back from the server as a response to
82 FTP servers return a 227-line as a response to a PASV command. If libcurl
107 returned to libcurl from a write callback.
122 specified a good enough address for libcurl to use. See
149 Aborted by callback. A callback returned "abort" to libcurl.
157 Too many redirects. When following redirects, libcurl hit the maximum amount.
160 An option passed to libcurl is not recognized/known. Refer to the appropriate
162 libcurl. The error buffer might contain more specific information about which
248 (For internal use only, will never be returned by libcurl) No connection
257 These error codes will never be returned. They were used in an old libcurl
260 This is the generic return code used by functions in the libcurl multi
279 This can only be returned if libcurl bugs. Please report it to us!
281 The passed-in socket is not a valid one that libcurl already knows about.
