The HTTP(s) check loads the text or other content specified by the URL according to RFC 2616 (HTTP/1.1). Both HTTP and HTTPS (HTTP over SSL) protocols are supported. The loaded content can be checked for the presence of a key word or phrase, and can be checked for changes since the last load. GET and POST methods are supported. Basic authentication is also supported.

Host - The fully qualified domain name or IP address of the server to be tested.

Monitor Description (optional) - Whatever you want to call this monitored service to uniquely identify it from the others.

Service Port - The port number the service you are testing is listening on. This defaults to the standard port of this service.

URL Path - The full URL including or file path. For FTP, this is the file path on the server to test for. For HTTP, this may also contain GET string variables if you choose. Also note that you can do a POST with GET string variables as well.

Request Method (optional) - This is either a GET, or a POST. A get is a standard request to a web server, a POST is what occurs when a form is submitted and therefore, data is expected by the web server to process. This defaults to a GET.

Request Content (optional) - Only applicable when using the POST method, you can enter key->value pairs to be posted to the site. This is good for checking logins and other forms that usually require user input.

Search String (optional) - You can scan the content from a web server request for keywords using absolute strings, or a PERL compatible regular expression. You can set whether to fail the test upon match, or no match of your keywords.

Search String Fail (optional) - When checked, the monitoring service will fail on a search string match, when unchecked, likewise will occur.

User Name (optional) - A login will be performed at the server to ensure authentication is functioning properly. If via HTTP(s), this will be using the Basic Auth. method, otherwise, whatever standard means applies to the protocol. A failed login will result in a failed test.

User Password (optional) - A login will be performed at the server to ensure authentication is functioning properly. If entered, this option also requires a user name or email address otherwise the this field will simply be ignored. If via HTTP(s), this will be using the Basic Auth. method, otherwise, whatever standard means applies to the protocol. A failed login will result in a failed test.

Use SSL/TLS (optional) - Perform tests for an SSL or TLS socket connection, whichever is appropriate for the service being tested.

Compare Checksum (optional) - A standard MD5 checksum is created on every page check, if a page changes, so will the checksum and our "Bee" will warn you that the page has changed.

Max. Timeout (optional) - The maximum number of seconds that our "Bees" will wait for a connection or to receive data, before the test is considered a failure.

Paranoid Mode (optional) - When enabled, our system will notify you if it finds any hiccups with the particular services that this feature is enabled on. Be careful, if the service you set paranoid on is quirky, you will get a lot of alerts!