"Craig R. McClanahan" wrote:
>
> The safe solution (and the only solution if you cannot control whether the user
> uses cookies or not) is to program your app to deal with the "two windows / one
> session" problem. One approach to this would be to embed a hidden variable in
> each form that is
Peter Alfors wrote:
> Sorry to keep this post going on, and on, and on...
> But I am still pretty confused.
>
> I am attempting to disable the cookies on the server side by using the
> "noCookies" attribute in the RequestInterceptor as follows:
>
>className="org.apache.tomcat.requ
Sorry to keep this post going on, and on, and on...
But I am still pretty confused.
I am attempting to disable the cookies on the server side by using the
"noCookies" attribute in the RequestInterceptor as follows:
My simple web page:
Session Id: <%= session.getId() %>
Peter Alfors wrote:
> When I run this, the session id's are still the same for two separate
> instances of netscape 4.7. (both instances started from the desktop).
> What am I missing to force the session id's to be different?
I assume from your headers that you're using windows - at least in
Win
Yep, since it has no JSessionID on the url, it must (by definition) be
without a session, so Tomcat creates one for it.
-Original Message-
From: Peter Alfors [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 4:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Session ids (netscape
Thanks for the response. From the messages below, it appears that problem is
not client-side.
It sounds like if a 'jsessionid' is not passed with the request, then Tomcat
will create a new session.
Is this correct?
Pete
Jim Crossley wrote:
> Hi Peter,
>
> Unfortunately, there's no foolproof wa
Hi Peter,
Unfortunately, there's no foolproof way to do what you're trying to do.
The limitation is imposed on the client-side. Your success depends on
how much control you have over your users, i.e. it becomes a training
issue.
A good description of the issues involved is on page 134 of Hans
