Thank you,Amos! Due to security reasom, Tomcat do not like to run as a root. I was using ipfw to forward port 443 to Tomcat's 8443 In my squid machine, I setup squid to listening 8443. When the index.jsp page work, it redirect the browser to https://tomcat:443/the redirected page, which is really the https://tomcat:8443/redirected page. If we can cache just a partial of a web site, such as http://host/one-context-of-tomcat Then we can resolve the problem becuase inside the context, I know there is not JSP page would redirect us again. I remember Apache can do this. But Apache to be a reverse proxy is terrible. Thanks! On Sun, Mar 15, 2009 at 4:36 AM, Amos Jeffries <squidI3@xxxxxxxxxxxxx> wrote: > fulan Peng wrote: >> >> Hi, >> When I want to cache a Tomcat site which its index.jsp has a command >> to redirect the browser to another pages, Squid is getting lost, the >> browser shows the redirected page but the port number is wrong. Is >> there any way to handle this situation? I am using Squid 3.0 and >> setting up a reverse proxy. >> Thanks! > > The tomcat JSP application does not sound to be proxy-aware. It's giving out > its internal ip/fqdn:port info rather than the public details it should. > > Best fix is to correct the JSP app to not care about its operating port. > > Hack fix #1, is to get tomcat listening on an internal IP port 80, so the > port does not get sent by the app. > > Hack fix #2, is to get Squid to listen on the public IP same ports as tomcat > is sending out. So as to catch back into sequence the visitors who get > redirected wrong. > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13 > Current Beta Squid 3.1.0.6 >
