Source string Source string

124/10000 · 124
English
Extra Alert Emails
You may specify here extra Emails to receive alerts for this test (comma separated)
Notes
Notes sent in email
External ID
Enter an Eternal ID for this Thold Template.
All fine. Proceed as usual.
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 did not use, it can be a misspelled protocol string or just a protocol libcurl has no code for.
Early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental could not get done at init time.
The URL was not properly formatted.
A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl.
Could not resolve proxy. The given proxy host could not be resolved.
Could not resolve host. The given remote host was not resolved.
Failed to connect() to host or proxy.
The server sent data libcurl could not parse. This error code was known as CURLE_FTP_WEIRD_SERVER_REPLY before 7.51.0.
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.

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:591
String age
7 months ago
Source string age
7 months ago
Translation file
locales/po/cacti.pot, string 165