Related Articles

SA43681 - 2016-11: CSRF vulnerability with Brocade Virtual Traffic Manager (vTM) (CVE-2016-8201)

SA43582 - Out-of-Cycle Advisory: Virtual Traffic Manager (vTM) Password Management Vulnerability/Sensitive Data Protection Vulnerability/Principle Of Least Privilege Violation

5761 - What determines when the virtual traffic manager clock syncs and how can this be controlled?

5878 - Traffic Manager agreeing with back-end when both http and https are in use

4614 - What is the meaning of the Virtual Traffic Manager error "Dropped connection, request exceeded max_client_buffer limit"

8224 - Virtual Traffic Manager (vTM) web UI displays "Cluster: Conflict" message briefly, then switches back to green OK status

SA43730 - 2018-04 Security Bulletin: Multiple vulnerabilities resolved in Pulse Connect Secure / Pulse Policy Secure 9.0R1 and vTM 18.1

14092 - What is the meaning of "no common SSL versions" in the error log of traffic manager devices?

SA44508 - 2020-06: Out-of-Cycle Advisory: Multiple Vulnerabilities in Treck TCP/IP Embedded Software

6403 - Does the virtual Traffic Manager software support SPDY 3.1, and if so, which versions support it?

< Back to search results

Article

5557 - X-Cluster-Client-IP header behavior with virtual traffic manager

« Go Back

Information

Last Modified Date	11/27/2017 4:26 PM

Synopsis

This article provides information about how X-Cluster-Client-IP header behaves with the vTM appliance.

Problem or Goal

Cause

Solution

Virtual Traffic Manager will behavior in two different ways with the X-Cluster-Client-IP header.

If the X-Cluster-Client-IP header is present, then the X-Cluster-Client-IP header will be overwritten.
If the X-Cluster-Client-IP header is not present, traffic manager will insert it.

Related Links

Attachment 1

Created By	VenkataKondaReddy Palem