Thanks for your answer. We have now put a header with nocache. One of the users that have reported the error of getting someone else data says that it works like it should so it seems like if the problem was in a proxy.
I would like to ask for tomcat as default to uses nocache since that is the behavior at least I assume that a dynamic webserver to have. But I'll guess that there are arguments to not to do that. But to me it seems more logically to tell when to allow caching then when not to since the reason to use dynamic webservers are that the pages changes. Thanks again all who have helped! Roland Carlsson ----- Original Message ----- From: "Ralph Einfeldt" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, August 14, 2002 12:35 PM Subject: AW: Session and IP > What makes you think that they share the session ? > > In mosts cases I have seen in the past this kind > of problems came from the application that stored > something in a way that wasn't session safe. > > On additional type of problem: > Pages with personalized data can sometimes be cached > by proxies, so make shure that you disable the caching > by setting the apropriate headers. > > > -----Urspr�ngliche Nachricht----- > > Von: Roland Carlsson [mailto:[EMAIL PROTECTED]] > > Gesendet: Mittwoch, 14. August 2002 11:20 > > An: Tomcat Users List > > Betreff: Session and IP > > > > The problem is that they seems to share the same session on > > our server. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
