Running a Caching Proxy server that is bound to an IP alias with the BindSpecific directive
 Technote (troubleshooting)
 
Problem(Abstract)
The IP alias to which the Caching Proxy is running "bind specific" does not appear in the SRC IP header of the packets going from the Caching Proxy server to the origin server.
 
Cause
Work as designed.
 
Resolving the problem
When running a Caching Proxy server that is bound to an IP alias with the BindSpecific directive set to on, the IP alias appears in the DEST header of IP packets going from the client to the Caching Proxy server.

The IP alias to which the Caching Proxy is running "bind specific" does not appear in the SRC IP header of the packets going from the Caching Proxy server to the origin server.

The main IP address of Network Interface Card (NIC) appears in the SRC IP header of the packets going from the Caching Proxy to the origin server.
 
 
Product Alias/Synonym
WTE
WSPP
Web Traffic Express
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Windows NT
Software version: Caching Proxy 4.0
Software edition:
Reference #: 1044314
IBM Group: Software Group
Modified date: Feb 6, 2006