Use Apache httpd in front of your servlet engine and have mod_proxy pipe
the requests from httpd to 1 servlet webapp. The session can remain in
Tomcat while Cocoon uses different stylings or sub sitemaps.
Just a thought.
Bert
On Tue, 2004-10-26 at 19:27, Oscar Picasso wrote:
> Hi,
>
> I have a
Thanks for the idea.
Actually I don't use apache httpd, but something that should behave similarly I
think.
I have only one servlet webapp (actually the cocoon instance) which already
serves the requests to the different sites.
The problem is that, even if the different sites are served by the s
ubject: Re: Sharing sessions and authentication across sites
Thanks for the idea.
Actually I don't use apache httpd, but something that should behave
similarly I
think.
I have only one servlet webapp (actually the cocoon instance) which already
serves the requests to the different sites.
> If you have "different sites" under the same webserver
> installation then sharing the authentication information
> between cocoon apps should be ok.
That's my configuration. It should be ok but in my case it's not.
So let me detail my config.
Both the server and the client I use to test have
I finally found a solution.
Sessions and authentication are shared between sites that use a same cocoon
instance. The problems lies in the access to the session id cookie.
Let's say we have:
first.mydomain.org
second.mydomain.org
I just had added the following in web.xml
org.mortbay.jetty.se
