Source string Source string

120/10000 · 120
English
We were denied access to the resource given in the URL. For FTP, this occurs while trying to change to the remote directory.
While waiting for the server to connect back when an active FTP session is used, an error code was sent over the control connection or similar.
After having sent the FTP password to the server, libcurl expects a proper reply. This error code indicates that an unexpected code was returned.
During an active FTP session while waiting for the server to connect, the CURLOPT_ACCEPTTIMEOUT_MS (or the internal default) timeout expired.
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 problem was detected in the HTTP2 framing layer. This is somewhat generic and can be one out of several problems, see the error buffer for details.
Received an error when trying to set the transfer mode to binary or ASCII.
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 does not match the previously given size.
This was either a weird reply to a 'RETR' command or a zero byte transfer complete.
Obsolete Error
Not used in modern versions.
When sending custom "QUOTE" commands to the remote server, one of the commands returned an error code that was 400 or higher (for FTP) or otherwise indicated unsuccessful completion of the command.
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.
Failed starting the upload. For FTP, the server typically denied the STOR command. The error buffer usually contains the server's explanation for this.
There was a problem reading a local file or an error returned by the read callback.
A memory allocation request failed. This is serious badness and things are severely screwed up if this ever occurs.
Operation timeout. The specified time-out period was reached according to the conditions.
The FTP PORT command returned error. This mostly happens when you have not specified a good enough address for libcurl to use. See CURLOPT_FTPPORT.
The FTP REST command returned error. This should never happen if the server is sane.
The 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.
The download could not be resumed because the specified offset was out of the file boundary.
A file given with FILE:// could not be opened. Most likely because the file path does not identify an existing file. Did you check file permissions?
LDAP cannot bind. LDAP bind operation failed.
LDAP search failed.
Function not found. A required zlib function was not found.
Aborted by callback. A callback returned "abort" to libcurl.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
Source string location
includes/arrays.php:647
String age
7 months ago
Source string age
7 months ago
Translation file
locales/po/cacti.pot, string 180