Alteon Application Switch Operating System Application Guide
Layer 7 String Handling
Document ID: RDWR-ALOS-V2900_AG1302
805
The following are example scenarios for which to use the Content Precedence Lookup feature:
•
If the client request is sent without a cookie and if no HTTP SLB is configured, then Alteon binds
the request to the real server using normal SLB.
•
If the client request is sent without a cookie, but HTTP SLB is configured on Alteon, then the
request is bound to real server based on HTTP SLB.
•
If the client request is sent with a cookie, and a real server associated to the cookie is found in
the local session table, then the request stays bound to that real server.
Requirements
•
Enable Direct Access Mode (DAM), or configure proxy IP address if DAM is disabled.
•
Enable delayed binding.
Using the or / and Operators
Figure 135 - Content Precedence Lookup Protectors Example, page 805
illustrates a network with
Real Servers 1 and 3 configured for URL SLB, and Real Servers 2 and 3 configured for HTTP Host
SLB.
Figure 135: Content Precedence Lookup Protectors Example
If you have configured Content Precedence Lookup with the or and and operators, the request from
the client is as follows:
•
HTTP Host or URL SLB—The HTTP Host header takes precedence because it is specified first.
If there is no Host Header information, and because or is the operator, the URL string is
examined next.
—
If a request from a client contains no Host Header but has a URL string (such as "/gold"),
the request is load balanced on Server 1 or Server 3.
—
If a request from a client contains a Host Header, then the request is load balanced between
Server 2 and Server 3. The URL string is ignored because the HTTP Host was specified and
matched first.
