libcurl-errors.md - OpenGrok cross reference for /curl/docs/libcurl/libcurl-errors.md

Lines Matching refs:error
22 libcurl-errors - error codes in libcurl
26 This man page includes most, if not all, available error codes in libcurl.
31 Almost all "easy" interface functions return a CURLcode error code. No matter
33 is a good idea as it gives you a human readable error string that may offer
34 more details about the cause of the error than just the error code.
35 curl_easy_strerror(3) can be called to get an error string from a given
53 Early initialization code failed. This is likely to be an internal error or
82 The server sent data libcurl could not parse. This error code was known as
93 used, an error code was sent over the control connection or similar.
98 reply. This error code indicates that an unexpected code was returned.
122 and can be one out of several problems, see the error buffer for details.
126 Received an error when trying to set the transfer mode to binary or ASCII.
139 ## Obsolete error (20)
146 returned an error code that was 400 or higher (for FTP) or otherwise
152 returns an error code that is \>= 400.
156 An error occurred when writing received data to a local file, or an error was
159 ## Obsolete error (24)
166 command. The error buffer usually contains the server's explanation for this.
170 There was a problem reading a local file or an error returned by the read
183 ## Obsolete error (29)
189 The FTP PORT command returned error. This mostly happens when you have not
195 The FTP REST command returned error. This should never happen if the server is
198 ## Obsolete error (32)
206 ## Obsolete error (34)
213 error buffer and read the message there as it pinpoints the problem slightly
235 ## Obsolete error (40)
239 ## Obsolete error (41)
251 ## Obsolete error (44)
257 Interface error. A specified outgoing interface could not be used. Set which
261 ## Obsolete error (46)
274 libcurl. The error buffer might contain more specific information about which
279 An option passed in to a setopt was wrongly formatted. See error message for
289 nothing is considered an error.
307 ## Obsolete error (57)
322 This error code has been unified with CURLE_SSL_CACERT since 7.62.0. Its
329 ## Obsolete error (62)
380 This error should never be returned by a properly functioning TFTP server.
382 ## Obsolete error (75-76)
396 An unspecified error occurred during the SSH session.
437 Chunk callback reported error.
454 Stream error in the HTTP/2 framing layer.
462 An authentication function returned an error.
467 be one out of several problems, see the error buffer for details.
471 QUIC connection error. This error may be caused by an SSL library error. QUIC
476 Proxy handshake error. CURLINFO_PROXY_ERROR(3) provides extra details on
485 An internal call to poll() or select() returned error that is not recoverable.
502 This is not really an error. It means you should call
559 A multi handle callback returned error.
563 An internal call to poll() or select() returned error that is not recoverable.
567 The "share" interface returns a **CURLSHcode** to indicate when an error has
598 The URL interface returns a *CURLUcode* to indicate when an error has
627 URL decode error, most likely because of rubbish in the input.
731 The header interface returns a *CURLHcode* to indicate when an error has