Hi Andre,
Thanks so much for the observation. Yes, The Redirect is redundant. I will
leave it in there for now though as this is not a recent change. I would like
to isolate what's causing "//".
I wanted to crank up logging in Tomcat side to catch the Request and Response
processing. I tried the RequestDumperValve. But the 302s were not being
caught.
Please let me know if there is a better way debugTomcat's request and response
processing.
I would like to find out how Tomcat processes requests for
"wwwprod.lsa.umich.edu/polisci" different from "www.lsa.umich.edu/polisci",
causing it to send a "//" for the latter.
Thanks.
-Shanti
On Sep 14, 2011, at 2:58 AM, André Warnier wrote:
> Shanti Suresh wrote:
>> All,
>> We are running into a peculiar issue. We have Tomcat 6.0.24 front-ended by
>> Apache2.2.3. We have a VirtuslHost serving port 80 where Apache simply
>> hands off "/" to Tomcat's load-balancer.
>> <VirtualHost *:80>
>> ServerName wwwprod.lsa.umich.edu
>> ServerAlias wwwprod www www.lsa.umich.edu
>> Redirect / balancer://dsmdelivery/
>> ProxyPass / balancer://dsmdelivery/
>> ProxyPassReverse / balancer://dsmdelivery/
>> TraceEnable Off
>> </VirtualHost>
> Why do you have a "Redirect" AND a "ProxyPass" above ?
> At least the Redirect doesn't make sense to me here.
> As written, it is also probably wrong :
> From http://httpd.apache.org/docs/2.2/mod/mod_alias.html#redirect :
> "The new URL should be an absolute URL beginning with a scheme and hostname,
> but a URL-path beginning with a slash may also be used, in which case the
> scheme and hostname of the current server will be added."
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> !DSPAM:4e7050e3221842560778728!
>
>
>
--
Shanti Suresh
App Systems Analyst Lead
Web Services, LSA Development
University of Michigan
Office: 734-763-4807
[email protected]
http://lsa.umich.edu/cms
