On 18 May 2012, at 20:38, Teo <teomina...@gmail.com> wrote: > Hi, > > first time posting on a mailing list, hope i'm not breaking any rules of > some sort. My problem is pretty simple but it seems a lot of people have > trouble understanding it in other forums.
Okay... > Let's say i have 2 main entry > points into my application: /subapp/a and /subapp/b. Ok > They are part of the > same webapp but they are somehow different and i want to distinguish > between them. Ok > Having a separate session for each of them would be the > greatest thing but is this possible for Tomcat? Yes, if they are separate applications. This is a Servlet Spec requirement. > The path of the session > cookie (JSESSIONID) is automatically put at the root context path (so > /subapp in this example). The word root has a special meaning, be precise please. It usually means ROOT - the default application whose path is '/'. I don't think that's what you intend. > And i don't want to have multiple wars or > multiple Tomcats... Why not? Work with the technology instead of against it. If you name your app: myapp#subappA.war The context & cookie path will be /myapp/subappA Problem solved. p > I would like this in Tomcat 7 btw... I'm trying to > avoid changing Tomcat itself so i tried to extend/wrap the usual response > classes/interfaces but no luck because Tomcat writes the Set-Cookie header > directly into the coyote response header... > > Any help would be appreciated, been wrestling with this for some days... > > Thanks, > Teo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
