Caching Proxy support of the host:port option on the ReversePass directive
 Technote (troubleshooting)
 
Problem(Abstract)
Caching Proxy uses the host:port option to apply different ReversePass rules based on the hostname and port of the backend server.

The minimum release levels that support this option are: 4.0.2.36, 5.0.2.13, 5.1.1.0, 6.0.2.0.
 
Resolving the problem
When you add host:port information in the ReversePass directive, Caching Proxy returns different redirect locations in the 302 (Found) responses for different backend servers.
Syntax:
ReversePass   url-pattern-returned-from-backend-server   external_proxy_server_url_pattern  [host:port]

Example:
ReversePass http://internal.server1.com/another_location http://proxy.server.com/server1_external_location    internal.server1.com:80

Note: The host is the hostname or IP address of the backend server. The port is the listening port of the backend server.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Edge Server Caching Proxy Multi-Platform Edge Server 2.0 PTF2
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Edge Component
Operating system(s): Windows
Software version: 6.0.2
Software edition:
Reference #: 1216532
IBM Group: Software Group
Modified date: Sep 8, 2005