Port Check Server Configuration


Detection of the following properties requires the use of a special virtual web site, referred to as the Port Check Server: SSLEnabled, Firewall, OpenPorts, ImagesEnabled, and SSLKeySize*.


Note: If you are not interested in detecting any of the above listed properties, no Port Check Server is required, and you may skip this section entirely.


Tip: Just starting to evaluate BrowserHawk? Skip this section and come back to it in the future. By default, BrowserHawk comes pre-configured to use cyScape’s Port Check Server. This enables you to test these advanced properties without having to set up your own Port Check Server (set up instructions provided below). This provides great convenience and ease during your evaluation of BrowserHawk and initial development. Before using these BrowserHawk tests in production, however, you need to configure your own Port Check Server.

What is a Port Check Server?


To perform the property checks mentioned above, BrowserHawk instructs the visitor’s browser to make a transparent request to another virtual web site instance, known as the Port Check Server, in conjunction with its testing.


The Port Check Server is simply a virtual web site instance, which can reside on the same machine as the web site where BrowserHawk is used from, or it can reside on another server altogether. The only requirement is that the Port Check Server web instance must be assigned its own IP address.


By default, and for your convenience, BrowserHawk is configured to use cyScape’s Port Check Server for these tests. This enables you to develop and test BrowserHawk’s full capabilities without having to set up your own Port Check Server first. However, cyScape’s Port Check Server is not designed for fault tolerance and maximum availability, and it is required that you set up your own Port Check Server prior to using these property checks in a production environment.


Note: By default, the OpenPorts check uses cyScape’s Port Check Server. At this time, this server is configured to handle detection of the following ports only: 80, 443, 554, 1755, 7070, 8080, 8081, and 9090. To check the status of any other port during your development and testing you must configure your own Port Check Server.


Important: It is not possible to perform these tests over a secure connection because tests involving the Port Check Server require BrowserHawk to pass data through a specific port. However, HTTPS data must pass only over port 443. Therefore it is not possible to satisfy both of these requirements. If these properties are tested from a HTTPS page it will result in a mixed security warning message from under Internet Explorer.

How do I configure my own Port Check Server?


Follow these steps to set up your own Port Check Server:


* Set up of the Port Check Server for SSLKeySize detection is required only when you use the extended property check approach for key size detection (Approach 2 as described in the SSLKeySize property documentation). If you wish to perform key size detection from HTTPS pages, there is no need to set up or use a Port Check Server in conjunction with your test.


See Also:

SSLKeySize Property

SSLEnabled Property

Firewall Property

OpenPorts Property