"Location" response header processing; HTTP vs. AJP

[edwinb1]

When HTTPD is configured to connect to Tomcat worker via HTTP, the resulting "Location" response header after initial request contains the address of the worker:

     Location=http://169.70.168.89:8089/myApp/jsp/myPage.jsp

As a side effect, browser reveals the worker's URL and the application no longer benefits from load balancing for subsequent requests. However, when  AJP is in effect, the "Location" response header is HTTPD's address and everything works as expected.

Is there a difference as to response header processing between AJP and HTTP?

Regards,

Edwin

[jfclere]

That is not a mod_cluster problem.

Try to use proxyName and proxyPort in the <Connector/>.