ons, 14,.12.2005 kl. 03.38 +0000, skrev Mark Borins: > After some more experimentation I have found that the route of the problem is > cookies. I downloaded that Live HTTP Headers plugin for firefox by your > recommendation. Everything seemed to look fine. But I noticed that no > matter > what user I logged in as the JSESSIONID cookie value was always the same. I > am > not sure if this is supposed to happen or not. > > But what I found is that when I disable cookies in my browser everything > works > fine. This seems to be because when cookies are disabled then Tapestry > simply > passes the JSESSIONID through a queryString parameter. > > So now I ask the Tapestry community. If I am having session problems and > disabling cookies seems to fix the issue. What kind of problem could I have? > > Is this a common problem? Anyone know any solutions?
I would guess that the cookie the server tries to set doesn't match the servers url-name. So if you use virtual hosts - the connector you use (given that you use tomcat) is naming the cookie with another server name than the url the request is made from. Then when you make a new request, the newly set cookie is not returned. Also you might have turned of the setting in your browser to accept cookies from 3. parties, thus refusing to set the wrongly named cookie. In the connector config of tomcat it is possible to specify which name you want the connector to pretend it is. E.g we use several tomcats in a cluster, where each box has dns 'server1,2,3' but all connector report they are from 'server'. http://tomcat.apache.org/tomcat-5.5-doc/config/http.html see proxyName. I have never configured virtual hosts in tomcat or in the jboss/tomcat combo you use. So how that will influence the naming of connectors I don't know. I hope I am on to something though... HTH -- Olve Hansen <[EMAIL PROTECTED]> InterMedia Bergen - Aksis / Unifob AS
signature.asc
Description: Dette er en digitalt signert meldingsdel
