What if:
1. load balancer receives a request for http://server/
2. does httpd return http://server:81/ in Location? (I don't think so)
And also what if
1. load balancer receives a request for http://server/somecontext/index.jsp?
Punky
Filip Hanik wrote:
I should also note that this scenario works fine if you remove Apache from
the stack.
so when the load balancer forwards to port 8080, the location uses port 80
to return with.
so maybe this is mod_jk that should list the port as 80?
Filip
here is a scenario
hardware stack
LoadBalancer(port80) - Apache/mod_jk 2.0.43(port81) - Tomcat
4.1.12(port8080/8009)
1. The load balancer receives a request for http://server/somecontext/
2. The load balancer forwards this to apache. Apache detects /somecontext/
and makes a request to Tomcat
3. Tomcat gets the request GET /somecontext/ and looks up welcome files
4. Tomcat finds index.jsp as a welcome file
5. Tomcat constructs a redirect using the absolute URL it got from Apache
and here is the problem, in step 5 tomcat constructs an absolute URL, and
uses the port number from Apache which was 81.
hence the redirect will go to port 81.
the response back to the server is
Location:http://server:81/somecontext/index.jsp --which is wrong, the
request came in on port 80
when it would have been better if the response was the relative URL.
Is this a bug, or could we add a feature to be able to configure the Coyote
connector to generate absolute or relative urls on sendRedirect
Filip
~
Namaste - I bow to the divine in you
~
Filip Hanik
Software Architect
www.filip.net
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
