The problem is, in IE (and Netscape) a ctrl+n is another Window on the same
browser session.
So you already have sessions restricted to one session! *g*
I doubt there is a good way around this. Even if you used Javascript
variables or hidden fields, if the users network connection is bad, then IE
will use a cached copy of the page, unless it's was received via an https
call (and I've seen it cache those too sometimes, a bug?).
You can maintain more state info on the server, such that multiple posts of
the exact same data are captured, etc. What you are seeing is the default
behaviour of the browser.
Thor HW
----- Original Message -----
From: Madhavi Karanam <[EMAIL PROTECTED]>
To: 'Thor HW' <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, November 24, 1999 3:31 PM
Subject: RE: sessions independent of browsers
> User can use it anyway, we cannot restrict his browser start up.
> I am looking for a way to restrict the session for one browser.
> Madhavi
>
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Thor
> HW
> Sent: Wednesday, November 24, 1999 5:59 PM
> To: [EMAIL PROTECTED]
> Subject: Re: sessions independent of browsers
>
>
> Don't use "ctrl+n". Start IE/Netscape again. You'll have a new session.
> Thor HW
> ----- Original Message -----
> From: David Medinets <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, November 24, 1999 12:52 PM
> Subject: Re: sessions independent of browsers
>
>
> > The simple answer is to use Netscape, IE, and Opera to allow you
> > to manipulate three sessions at a time. Each browsers mantains its
> > own set of cookies.
> >
> > On Wed, 24 Nov 1999, Madhavi Karanam wrote:
> >
> > > When we do a "ctrl + n", we get a new browser window. Session gets
> copied
> > > for the new window. Is there anyway to restrict to one window. Session
> > > behaves weird in these cases. If we logoff from one window and logon
> with
> > > different user-id then the old window also responds to the new
user-id.
> Any
> > > information about this would be of great help for me.
> > > Madhavi
> > >
> > >
> > > -----Original Message-----
> > > From: A mailing list for discussion about Sun Microsystem's Java
Servlet
> > > API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Dr.
> > > Dragomir D. Dimitrijevic
> > > Sent: Wednesday, November 24, 1999 9:20 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: sessions independent of browsers
> > >
> > >
> > > Hi All,
> > >
> > > Does anyone know how to maintain a session (so I can store
> > > objects in the session object) whwn servlet's client is
> > > another servlet on another web site. The client servlet uses
> > > the code below to post a Java object as a request.
> > > The response comes back as a response java object
> > > The code below works OK. I just need to add
> > > maintenance of sessions.
> > > I use Apache/Jserv. How I send back the information about
> > > the current session. I guess the client server needs to
> > > retreive/save and send back the JservSessionId cookie.
> > >
> > > Any suggestion will be apprecated.
> > >
> > > Happy Thanksgiving to folks in the US.
> > >
> > > Dragomir
> > >
> > >
> > > public AuthResponse authorize(
> > > Serializable req )
> > > throws IOException, ClassNotFoundException
> > > {
> > > URLConnection con = authURL.openConnection();
> > >
> > > con.setDoInput(true);
> > > con.setDoOutput(true);
> > > con.setUseCaches(false);
> > > con.setRequestProperty(
> > > "Content-Type",
> > > "java-internal/" + req.getClass().getName());
> > > ObjectOutputStream out = new
> > > ObjectOutputStream(con.getOutputStream());
> > > out.writeObject(req);
> > > out.flush();
> > > out.close();
> > > InputStream in = con.getInputStream();
> > > ObjectInputStream r = new ObjectInputStream(in);
> > > return (AuthResponse)r.readObject();
> > > }
> > >
> > >
>
___________________________________________________________________________
> > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > > of the message "signoff SERVLET-INTEREST".
> > >
> > > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > > Resources:
http://java.sun.com/products/servlet/external-resources.html
> > > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> > >
> > >
>
___________________________________________________________________________
> > > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > > of the message "signoff SERVLET-INTEREST".
> > >
> > > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > > Resources:
http://java.sun.com/products/servlet/external-resources.html
> > > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> > >
> >
> >
>
___________________________________________________________________________
> > To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> > of the message "signoff SERVLET-INTEREST".
> >
> > Archives: http://archives.java.sun.com/archives/servlet-interest.html
> > Resources: http://java.sun.com/products/servlet/external-resources.html
> > LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
> >
>
>
___________________________________________________________________________
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
