4. Website configuration

Now configure a website.

  1. Select Services->Websites in the left menu pane. This will take you to the websites overview page.

  2. Click on the Add Website button.

The Services->Add page is displayed.

Add website page

Figure 1.3. Add website page


In the Virtual web server section you configure the part of the website proxy that the clients connect to.

  1. In Web server protocol select either HTTP, HTTPS or Both. The latter will create a website proxy that responds to both HTTP and HTTPS requests.

    When selecting HTTPS or Both as the protocol a temporary certificate will be generated. When the new proxy is created the certificate can be replaced by importing the real certificate in Services->Websites->ADC->Virtual host. Click Help in that section to get instructions.

  2. In Web server domain name enter the address of the web server you want to protect. The address is the one users enter in the browser to go to the website.

    In the example demosite.mydomain.com is entered.

  3. In Listen IP select the IP address you want the web server to respond to. For HTTP websites All inbound can be selected. This will configure the website proxy to respond to all IP addresses that are configured to accept inbound requests. For HTTPS proxies it is mandatory to select a specific IP address.

  4. In HTTP(s) listen port select the port(s) you want the website to listen to. For HTTP proxies the default is 80 and for HTTPS proxies the default is 443. When creating a website proxy that serves both HTTP and HTTPS two input fields will appear.

In the Real web servers section you configure how the website proxy communicates with the backend web servers.

  1. In Real web server enter the address of the web server you want Web Security Manager to redirect allowed client requests to. This address is the address of the web server you want to protect. In the example 192.168.0.103 is entered.

  2. In Real server protocol select the protocol you want Web Security Manager to use when connecting to the backend web servers. If you want the traffic to the backend web servers to be encrypted select HTTPS otherwise leave it at the default HTTP.

    Note that you should only select HTTPS if it is necessary. HTTPS puts an extra burden on the backend web servers.

  3. Decide on real servers health checking. When Validate real servers and enable health checking is checked Web Security Manager will connect to the backend servers automatically find a suitable target page to use for health checking. If health checking is not enabled backend server status will not be monitored by Web Security Manager.

  4. For each backend web server that is serving the website (demosite.mydomain.com in this example) enter the IP address and port in the real servers list.

    Real server IP and Port: the IP address / port combination the web server is listening on. Typically Address:80 for HTTP servers and Address:443 for HTTPS servers.

    Role: Select Active, Backup or Down. Active means that requests will be forwarded to the server. When Backup is selected the server will only be used if no Active servers are in operation. Down means that the server should not be used - for instance if it is down for maintenance.

Finally, In the Initial configuration section, select the initial configuration template to apply to the website proxy.

Now click the Save Configuration button in the lower right corner of the page.

This will save your configurations and take you back to the websites overview page.

  1. Click the blinking link apply changes that appears in the upper right corner of the page to apply those changes to your configuration of Web Security Manager.

Websites overview page

Figure 1.4. Websites overview page


The Web Security Manager Web Application Firewall is now protecting the configured website.

© 2005 - 2012 Alert Logic inc.