The web server configuration determines how Access Gateway handles connections and packets between itself and the web servers.
IMPORTANT:For caching to work correctly, the web servers must be configured to maintain a valid time. They must be configured to use an NTP server.
Click Access Gateways > Edit > [Name of Reverse Proxy] > [Name of Proxy Service] > Web Servers.
Specify the hostname that is placed in the HTTP header of the packets being sent to the web servers. In the Host Header field, select one of the following:
Forward Received Host Name: Indicates that you want the HTTP header to contain the published DNS name that the user sent in the request.
Web Server Host Name: Indicates that you want the published DNS name that the user sent in the request to be replaced by the DNS name of the web server. Use the Web Server Host Name field to specify this name. You can also append the port number to the Web Server Host Name field. For example, <web server hostname>:<web server port number>.
Select Error on DNS Mismatch to have the proxy determine whether the proxy service must compare the hostname in the DNS header that came from the browser with the DNS name specified in the Web Server Host Name option. The value in the parentheses is the value that comes in the header from the browser.
If you enable this option and the names don't match, the request is not forwarded to the web server. Instead, the proxy service returns an error to the requesting browser. This option is only available when you select to send the Web Server Host Name in the HTTP header.
NOTE:The Error on DNS Mismatch option does not work in the following scenarios:
If the option is enabled in a protected resource.
If the option is enabled in a master host based service, and disabled in a path-based child services, then Access Gateway does a strict check of DNS match for path-based child.
If your browsers are capable of sending HTTP 1.1 requests, configure the following fields to match your web servers:
Enable Force HTTP 1.0 to Origin: Indicates whether HTTP 1.1 requests from browsers are translated to HTTP 1.0 requests before sending them to the web server. If your browsers are sending HTTP 1.1 requests and your web server can only handle HTTP 1.0 requests, you must enable this option.
When the option is enabled, Access Gateway translates an HTTP 1.1 request to an HTTP 1.0 request.
Enable Session Stickiness: Selecting this option makes the proxy server to use the same web server for all fills during a session.
To enable SSL connections between the proxy service and its web servers, select Connect Using SSL. For configuration information for this option, Web Server Trusted Root, and SSL Mutual Certificate, see Section 20.6, Configuring SSL between the Proxy Service and the Web Servers.
In the Connect Port field, specify the port that Access Gateway must use to communicate with the web servers. The following table lists some default port values for common types of web servers:
|
Server Type |
Non-Secure Port |
Secure Port |
|---|---|---|
|
Web server with HTML content |
80 |
443 |
|
WebSphere |
9080 |
9443 |
|
JBoss |
8080 |
8443 |
To control how idle and unresponsive web server connections are handled and to optimize these processes for your network, select TCP Connect Options. For more information, see Configuring TCP Connect Options for Web Servers.
To add a web server, click New in the Web Server List and specify the IP address or the fully qualified DNS name of the web server.
The web servers added to this list must contain identical web content. Configuring your system with multiple servers with the same content adds fault tolerance and increases the speed for processing requests. For more information about this process, see Configuring Web Servers.
To delete a web server, select the web server, then click Delete.
This deletes the web server from the list so that Access Gateway no longer sends requests to the deleted web server. At least one web server must remain in the list. You must delete the proxy service to remove the last server in the list.
NOTE:Do not remove all configured web servers to the cluster if any of the cluster member does not have at least one web server configured.
To save your changes to browser cache, click OK.
To apply your changes, click the Access Gateways link, then click Update > OK.