Gerritjan Koekkoek schrieb:
Hello,
> In our test situation all works fine, but we get the problem on our
> live site.
> The live site is different from test site :
> Test site url like localhost:8080/cocoon/cdls/info_index.html
> Live site url like www.xxxx.org/info_index.html (using mod_proxy, see
> configuration below)
>
> Also in our sitemap we had to change the uri's; adding a '/' ; so "/
> aanmeldfout.html"/> on live site, "aanmeldfout.html"/> on test site
>
> We suspect a COOKIE problem, because the cookie from our live site
> contains a path /cocoon
I suppose this is the problem, yes...
> In Tomcat's server.xml a connector is declared for every cocoon site
> like this:
>
> <Connector port="8085"
> proxyName="www.cdls-nl.org" proxyPort="80"
> maxThreads="20" minSpareThreads="5" maxSpareThreads="10"/>
You can tell tomcat to set the SessionPath to "/" if that is the problem.
emptySessionPath="true"
> Tomcat listens to port 8080.
^^^^
This does not match the Connector (8085)
> If the proxy rules are changed into
>
> ProxyPass / http://localhost:8080/cocoon/cdls/
> ProxyPassReverse / http://localhost:8080/cocoon/cdls/
^^^^
Why 8080 here and not 8085?
> and Apache is restarted, the problem still exists.
>
> I don't know if we need these connectors.
Which ones?
And why don't you use mod_jk to connect apache&tomcat?
> The site runs SuSE Linux 9.2 on a Pentium pc with Sun Java 1.4.2,
> Tomcat 5.0
> and Cocoon 2.1.7
HTH
Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]