Then I modified the ProxyPass settings and used the jetty web.xml trick to change the cookie path.
Now, the interesting thing was that while /A performed just like before, /B had a wierd problem: "redirects" were absolute to the "webapp server", not to the "web server".
Both apps had the same exact version of cocoon (compiled this morning).
After careful examination and extensive protocol dump, I was able to understand that while /A used
cocoon.redirectTo(../../index);
/B used
cocoon.redirectTo(/index);
and both turn up to the in the same position, but while the first actually works (the redirect is "remapped" to the original Proxy URL, not to the appserver one which is obviously firewalled), the second doesn't do remapping and the web application fails because it tries to connect to the webapp directly
[actually it's even worse, because it tries to connect to the ProxyPass setting, which are http://localhost:8000/ in my case, so it tries to connect to *your* machine!]
The interesting thing is that this worked perfectly in the past, when both were mapped to /, but I can't tell what broke since I moved them *and* change the version of cocoon at the same time.
Did anybody experience a similar behavior?
-- Stefano.
