• Introduction
• How To Deploy
• Step-by-Step Guide
• Administration
• Administration
• General Options
• System Policies
• Users
• Users
• Manage Users
• Editing Users
• Registring the Program
• Managing Licenses
• Interface
• Main Menu
• Main Window Interface
• Toolbar
• Views
• Network Diagram
• Network Diagram
• Network Scanner
• Network Node Properties
• Agents
• Agents
• Managing Agents
• Agent Options
• Tests
• Tests
• Creating Tests
• Test Properties
• Test Variables
• Duplicating Tests
• Test Types
• CPU Usage Test
• Device Status Monitoring Test
• Drive Free Space Test
• ICMP Ping Test
• File Integrity Test
• File/Folder Size Test
• Firebird Database Connection Test
• HTTP Request Test
• MSSQL Database Connection Test
• MySQL Database Connection Test
• Network Traffic Monitor Test
• Oracle Database Connection Test
• POP3 Server Test
• Process Memory Test
• SNMP Get Test
• TCP Connection Test
• Windows Services Test
• Windows Update Test
• WMI Test
• Mib Browser
• MIB Browser
• MIB Browser Interface
• MIB Browser Menu
• MIB Browser SNMP Profiles
• Actions
• Actions
• Managing Actions
• Creating Actions
• Action Properties
• Schedule

System PulseMeter HTTP Request Test

HTTP Request Test

HTTP request test can be used for monitoring Web servers (HTTP / HTTPS) responses.

HTTP Request Test Properties

Basic HTTP Properties

• URL - the monitored URL.
• Authorization required - check whether the monitored URL requires authorization.
• User Name - the login user name for authorization.
• Password - the password for authorization.
• Timeout - adjust the value to change timeout of the HTTP test. Default HTTP request test timeout is set to 2.000 milliseconds.
• Follow redirects - check this option to allow following redirects between monitored resources.

Advanced HTTP Properties

• Request - the type of the request command sent to the monitored web server. The request command can be:
  • HEAD - use HEAD request for checking HTTP header of the monitored URL. Using HEAD request you can monitor HTTP document status information contained in the HTTP header. The server doesn't return a message-body in the response to the command.
  • GET - the GET request command can be used for checking HTTP headers and receiving data depending on data set with the command.
  • POST - the POST request command is used to transfer data to the monitored web server in order to receive a reply. The sent data should be written in the "POST Data" field. The sent data usually is processed by an application placed on the server so the response is usually a program output.
• POST Data - in case if the request command is set to POST you can define the data sent in the POST request. The data should be written is the standard form, for example:  parameter1=value1&parameter2=value2
• Allow cookies - check this option to allow using cookies for monitoring the web server.
• Custom headers - in this field you can form headers that will be added to the HTTP request. Custom headers can be used for sending cookies, accept-ranges, allow, authorization, content-length and other standard HTTP headers. The default custom headers are:
  User-Agent: Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1)
  Cache-Control: no-cache
  Accept-Language: en-us

Condition

• Test passes if - select the conditions of test passing. Conditions consist of sets of web servers response codes. Codes can be added manually or selected from the "Select error codes" dialog. The codes can be reset to "Default" by clicking the correspondent "D" button.
  • Response code IS in the set of the values below - form a set of response code values that will be considered as a successful result. The set can be formed with the help of the "Select error codes" dialog. Each reply code in the dialog has a title for more convenient selection.
  • Response code IS NOT in the set of the values below - form a set of response code values receiving which the test will be considered as failed.