Apache Server Status Test

This indicates how often should the test be executed.

The host for which the test is to be configured.

The port to which the specified host listens

In the this text box, the URL to be accessed by this test for extracting the Apache web server's performance statistics, will be displayed by default. The URL is: http://{Apache web server host}:{Apache web server port}/server-status.

Whether any cookies being returned by the web server need to be saved locally and returned with subsequent requests

The host on which a web proxy server is running (in case a proxy server is to be used)

The port number on which the web proxy server is listening

The user name of the proxy server

The password of the proxy server

Confirm the password by retyping it here.

Sometimes the eG agent has to parse the URL content with specific encoding other than the default (ISO-8859-1) encoding. In such a case, specify the type of encoding using which the eG agent can parse the URL content in the Encoding text box. By default, this value is none.

SSL-enabled web sites are typically secured by a private key, public key, or a public-private key pair. If the web page configured for this test is SSL-enabled – i.e., if an HTTPS URL is specified against URL – and the contents of this web page can only be accessed using a private key, then the full path to the private key file will have to be provided against Privatekey File Path and the password of the private key file should be specified against Privatekey Password. If no such private key protects the contents of the configured URL, then set the Privatekey File Path and its Privatekey Password to none.

Some web pages (URLs) configured for monitoring may have been designed to allow access for only those requests that have certain specific properties enabled. For instance, web pages of an SSL-enabled web site may have been designed to support TLS v1.3 requests alone. In such a case, you will have to instruct the test to send connection requests to the configured URL over the TLS v1.3 protocol alone; if not, the test will fail. For this, you can use the System Properties parameter. Clicking on the icon corresponding to this parameter will invoke Figure 1.

Figure 1 : Configuring System Properties

Specify the request property that the test needs to look up, in the Property text box of Figure 1. In the Value text box, enter the value this property should be set to, so that the eG agent is allowed access to the configured web page. In the case of the above example, you will have to specify -Dhttps.protocol in the Property text box and TLSv1.3 in the Value text box. You can even provide a comma-separated list of values in the Value text box. For example, if the web page supports multiple versions of the TLS protocol, then the Value specification will be: TLSv1.1,TLSv1.2,TLSv1.3.

You can even configure more than one Property:Value pair, if the configured URL supports multiple properties. To add another pair, click on the Add More button in Figure 1, Another Property:Value row will appear, where you can provide another system property that the test should use when accessing the given URL. You can delete any Property:Value specification by clicking on the encircled '-' button alongside that specification in Figure 1. To clear all the system properties that have been configured, click on the Clear button in Figure 1.

A user agent is a computer program representing a person - for example, a browser in a Web context. Besides a browser, a user agent could be a bot scraping webpages, a download manager, or another app accessing the Web. Along with each request they make to the server, browsers include a self-identifying User-Agent HTTP header called a user agent (UA) string. This string often identifies the browser, its version number, and its host operating system.

Some web sites may have been designed to service only those access requests that contain the User Agent (UA) string in the HTTP request header.  If this test has been configured with the URL of such a web site/web page, then you have to instruct the test to include the UA string in the header of every connection request it sends to the configured URL; if this is not done, then the test will fail. In this case therefore, set the value of the Include UserAgent in Header flag to true. By default, this flag is set to false, indicating that the requests this test emulates do not contain the UA string by default.