7.3

Option Description and algorithm parameters
HTTPHEADER The HTTP header name is looked up in each HTTP request.
The header name in parenthesis is not case sensitive which is similar to the ACL
'hdr()' function.
The HTTPHEADER algorithm parameter has one option headerName=<name>.
For example, you can use host as the HTTPHEADER algorithm parameter.
If the header is absent or does not contain any value, the round robin algorithm is
applied.
URL The URL parameter specified in the argument is looked up in the query string of
each HTTP GET request.
The URL algorithm parameter has one option urlParam=<url>.
If the parameter is followed by an equal sign = and a value, then the value is
hashed and divided by the total weight of the running servers. The result
designates which server receives the request. This process is used to track user
identifiers in requests and ensure that a same user ID is always sent to the same
server as long as no server goes up or down.
If no value or parameter is found, then a round robin algorithm is applied.
4 (Optional) Select the persistence method for this pool.
Persistence tracks and stores session data, such as the specific pool member that serviced a client
request. With persistence, client requests are directed to the same pool member for the life of a
session or during subsequent sessions.
Protocol Persistence method supported
HTTP None, Cookie, Source IP
HTTPS None, Source IP and SSL Session ID
TCP None, Source IP, MSRDP
UDP None, Source IP
n
Select Cookie to insert a unique cookie to identify the session the first time a client accesses the
site. The cookie is referred in subsequent requests to persist the connection to the appropriate
server.
n
Select Source IP to track sessions based on the source IP address. When a client requests a
connection to a virtual server that supports source address affinity persistence, the load balancer
checks to see if that client previously connected, and if so, returns the client to the same pool
member.
n
Select SSL Session ID and select the SSL Passthrough HTTPS traffic pattern.
n
SSL Passthrough - Client -> HTTPS-> LB (SSL passthrough) -> HTTPS -> server
n
Client - HTTP-> LB -> HTTP -> servers
Note vRealize Automation currently supports SSL Passthrough only. The SSL Passthrough
method is used regardless of which option you select.
Configuring vRealize Automation
VMware, Inc. 401