Upayavira wrote:
Basically, you've got to get Jetty (or tomcat) to mount the webapp without the /cocoon/. Then, you mount your app on /, so that http://localhost:8080/ is your application, so that:
http://mycocoonhost/ maps to http://localhost:8080/
Yes, that's what I thought. It's a pain though, I would have much preferred that mod_proxy also rewrite the cookie path.
The more complex stuff I was talking about was how to manage more than one webapp mounted onto different domain names.
AFAICS you won't be able to do that with cookie-based sessions just because of that cookie problem : you only have one root webpath to map to. Unless you mount every app in the root of its own domain name. Which is just what you were saying in the last mail... Ok, it took a while to get it :)
What servlet container are you using? Jetty or Tomcat?
> Then we can look at how to reconfigure it to do that.
I'm on Tomcat; no problem about reconfiguring things, thanks; it's just that deploying a webapp in the webapps/ directory is so much simpler.
What's with Jetty, I never tried it: is it simpler, is it faster or what ?
Regards, Adrian.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
