Loop-Detection; Max-Message-Size - IBM WebSphere XS40 Command Reference Manual

Datapower xml security gateway
Table of Contents

Advertisement

Uses the client IP address
Parameters
header Specifies the name of the HTTP header.
Guidelines
The load-balancer-hash-header command identifies the HTTP header to use for
calculating the hash for load balancing traffic to the backend servers.
v When defined, the hash algorithm uses the value of the identified HTTP header.
v When not defined, the hash algorithm uses the IP address of the client.
This command is relevant only when the value defined by the algorithm command
in Load Balancer configuration mode is hash.
Use the no load-balancer-hash-header command to disable the use of an HTTP
header as the hash algorithm to use for load balancing.
Related Commands
algorithm
Examples
v Disables the use of an HTTP header for load balancing (uses the IP address to

loop-detection

Enables or disables the loop detection algorithm.
Syntax
Enables the loop detection algorithm
Disables the loop detection algorithm
Guidelines
Some protocols provide a loop detection mechanism that can be used to detect
network loops. This is a good policy, but it can cause each proxy to be publicly
recorded in the transmitted message, which might be considered an information
leak.
By default, the loop detection algorithm is disabled.

max-message-size

Specifies the maximum size of an XML document to accept.
798
Command Reference
no load-balancer-hash-header
calculate the hash). Subsequently, enables load balancing traffic to the backend
servers using a hash algorithm identified by the X-Forwarded-For HTTP header.
# no load-balancer-hash-header
. .
.
# load-balancer-hash-header X-Forwarded-For
#
loop-detection
no loop-detection

Advertisement

Table of Contents
loading

Table of Contents