You can either put you CAS web app to the "ROOT" webapp directory so that the "/foo" on apache matches the "/foo" on tomcat ;
or you can add a rewrite rule so that /foo on the apache will be redirected to /cas/foo on the tomcat server : RewriteRule ^/(.*)$ ajp://xxxxx/cas/$1 [P,L] (I don't have mod_proxy_ajp to test it but it should work, although you might have some trouble with cookies beeing specified on "/cas/" and not on "/" ...) Romain Andrew R Feller a écrit : > While setting up the Apache HTTP server to forward requests to Apache > Tomcat, we wanted it such that CAS was the document root of the server > so requests would look like: > > > > http://ssoA.example.com/login?null > > http://ssoA.example.com/serviceValidate?.... > > > > I set up mod_proxy_ajp to forward all requests for document root to the > CAS web app, however, whenever I hit the server directly, it redirects > the traffic to /cas/login?null. > > > > How can I change this behavior to not send requests to /cas/? Should I > add a rule in the SimpleUrlHandlerMapping such that any request for > document root be picked up by the loginController? > > > > Thanks, > > > > Andrew R Feller, Analyst > > Subversion Administrator > > University Information Systems > > Louisiana State University > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > (office) 225.578.3737 > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
