views:

68

answers:

0

We have a tomcat application which works fine in IE7/8 and Firefox. The only browser we are having issues with (that we care about at this point) is google Chrome. Users can navigate to the application fine and log in and do whatever they need to do in Firefox and IE. However, when trying to log in with Chrome, the session is apparently lost immediately after log in and when the authenticated user tries to navigate to another page they are bumped back to the log in page. This happens consistently.

I have seen other entries here and elsewhere that suggest that the context path might be to blame. I have tried setting a ProxyReverseCookiePath but that does not fix the problem.

Our virtual host configuration is as follows:

<VirtualHost xxx.xxx.xxx.xxx:80>
    ServerAdmin [email protected]
    ServerName subdomain.example.com

    DocumentRoot /var/www

    ProxyRequests Off
    <Proxy *>
        Order deny,allow
        Allow from all
    </Proxy>


    ProxyPass /context/ ajp://127.0.0.1:8009/context/
    ProxyPass / ajp://127.0.0.1:8009/context/
    #ProxyPassReverse /context/ http://127.0.0.1:8009/context/
    #ProxyPassReverse / http://127.0.0.1:8009/context/
    #ProxyPassReverseCookiePath /context/ /

</VirtualHost>

There is another application deployed on the same instance of tomcat at the ROOT context. I have looked at the JSESSIONID that is set in the cookie, which is sent back to Chrome and it changes on every request, while it does not for IE and Firefox.

I am at a loss here. Any ideas are welcome!

We are using tomcat 6.0.23 as well as apache 2.2.14

related questions