Actually there is special code in Jahia that doesn't cache the page if
it detects that the jsessionID was generated by the servlet container
when encoding URLs. This is a requirement for proper handling of
sessions when users browse a site with cookies deactivated or with
cookies filtered. If you want to force cookie usage, you might want to
look into Tomcat configuration to see if there is a way to do that.
Regards,
Serge Huber.
Stéphane Croisier wrote:
Mmh, you also have the jsessionid in the demo. I just typed
demo.jahia.org and if you take a look on the generated urls the first
time you connect, all of them have the jsessionid parameter. This is
not managed by Jahia but by the servlet container and the Java spec...
Stéphane
At 11:03 27/06/2005, you wrote:
Hello!
On the very first request from a browser the created URLs in the page
are created with URL rewriting and a jsessionid is appended. Thus the
pages are not read from cache. On the next requests the server finds
out, that the browser supports cookies and does not use URL rewriting
anymore.
On your Jahia demo the jessionid is not appended even on first
request. Can you please tell us, how you solved this?
Greetings,
Benjamin Papez
