ServerIron ADX Server Load Balancing Guide
Release 12.0.00
June 15, 2009

Table of Contents Previous Next Print


Server Load Balancing > HTTP Redirect

HTTP Redirect
The remote server support and NAT support described in previous sections allow you to configure geographically-distributed servers that the ServerIron ADX uses as failovers if the local servers are unavailable. A typical configuration with geographically-distributed servers uses source NAT to cause responses from the remote real server to go back to the ServerIron ADX instead of directly to the client. This traffic pattern matches the standard traffic pattern among the ServerIron ADX, the clients, and the real servers.
However, if the links between a remote server and ServerIron ADX are slow and would introduce unacceptable delays, you can enable HTTP redirect. HTTP redirect configures the ServerIron ADX to send an HTTP redirect message to a client when the ServerIron ADX is sending the client's request to a remote server. The HTTP redirect instructs the client to redirect its TCP connection from the VIP to the real IP address of the remote server. After a successful HTTP redirect, the client and remote server communicate directly, not through the ServerIron ADX.
NOTE: If a client creates a bookmark when communicating directly with a remote server, the bookmark points to the real IP address of the server instead of the VIP. If the client uses the bookmark later to re-access the server, the client bypasses the VIP.

Server Load Balancing > HTTP Redirect

Table of Contents Previous Next Print
Copyright © 2009 Brocade Communications Systems, Inc.