Knowledge Articles
Security Advisories
Related Articles
TN44022 - Pulse One On-Prem Appliance Configuration Groups page group pannel displays loading image constantly
SA44790 - HTTP Request Smuggling vulnerability with Virtual Traffic Manager (vTM)
TSB44850 - Technical Support Bulletin - CISA Alert July 21st 2021
TSB44329 - EOL notification for Pulse Secure Steel-Belted Radius (SBR)
TSB44876 - On some macOS endpoints, it is observed that the Pulse Desktop Client & browser based applications are affected.
TSB44856 - Pulse Secure R12 Release and Pulse Techpubs Update
TSB43886 - Important information about Pulse Secure Mobile App on iOS 12 devices
SA43681 - 2016-11: CSRF vulnerability with Brocade Virtual Traffic Manager (vTM) (CVE-2016-8201)
TSB40604 - Support notification for Pulse Connect Secure features that are based on Java applets
TN40108 - Wireless Suppression fails when wireless Group policy objects (GPOs) are used
What would you like to know?
Reset Search
Search
< Back to search results
5557 - X-Cluster-Client-IP header behavior with virtual traffic manager
Printable View
«
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
Feedback
Was this article helpful?
Feedback
Please tell us how we can make this article more useful.
Characters Remaining:
255