The Previous Page property defines those pages which must have been visited
at some point during the session before the page to which it belongs is
accessed. The page defined in the Previous Page property may have been
visited at any time during the session, not necessarily right before the
page to which it belongs is loaded.
My understanding is that, if a valid session does not exist, the session is
created. Returning STOP from either the onSessionTimeoutEvent or a web
event prevents the PE from being updated with the new session information.
(It seems that I verified this using the log viewer at some point, but I
can't say for certain that it still holds true. If I'm wrong in this, I'd
be happy to hear that I'm wrong. This could be pretty bad if I'm wrong!)
I typically handle session timeouts as follows:
1. Customize the project onSessionTimeoutEvent to load the login page.
Return STOP from this event to prevent the new session from getting stored
in the PE.
2. Customize the login page to reload the login page for failed login
attempts and return STOP to prevent the session from getting stored in the
PE.
3. Set the Previous Page property for all pages so that the login page must
be accessed first.
== Grace
Vishal Gautam <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> Thanks for the reply, It worked to the extent that login page
> no longer gets timed out but I can not go to the pages via hyperlinks
> those have 'Login page' in their 'previous page' property.
> Could any body tell how excatly the previous page property works?
>
> TIA
>
> Vishal
>
>
> "DARREN KHOO, CUSD" <[EMAIL PROTECTED]> wrote:
> >> I guess I am able to answer #2.
> >>
> >> To prevent a user who left the login screen for too long from hitting
> >> time-out the moment he logs in, you can remove the spidersession tag
from
> >> the page or comment it out using html comment style and then put a form
> >> closing tag in its place.
> >>
> >> With that, your page will not contain a session id and when the user
> >> submits
> >> the login form, it will be treated as a new session.
> >>
> >> <HTML>
> >> <BODY>
> >> [[SPIDERPAGE NAME=PgLogin]]
> >>
> >> :
> >>
> >> <!-- comment out the spidersession tag
> >> **SPIDERSESSION**
> >> add a form closing tag below-->
> >> </form>
> >>
> >> [[/SPIDERPAGE]]
> >>
> >> </BODY>
> >> </HTML>
> >>
> >> -----Original Message-----
> >> From: Vishal Gautam [SMTP:[EMAIL PROTECTED]]
> >> Sent: Wednesday, July 14, 1999 4:08 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: [ND] How to creat a new session only on successful login?
> >>
> >>
> >> Hi Eveybody,
> >>
> >> I have a login page built in ND as the first page of the system so
> >> a session starts as soon as somebody hits this page, there are 2
> >> caveats in this-
> >> 1. The unsuccessful logins leaves a lot of orphan sessions in ND.
> >> 2. If a user leaves his machine at login page and comes after
> >> the time out, he/she does'nt like the idea of session getting
> >> expired before the login.
> >>
> >> I think I can use CSpider.removeUserSession() for the #1 but I
> >> need some suggestions for the #2. Is it possible to make a
> >> login page outside of ND and that would send the form results (loginID
&
> >> pwd)
> >> to ND's security Objects on submit so that atleast accessing login
> >> page will not start a new session.
> >>
> >> TIA
> >>
> >> Vishal
> >>
_________________________________________________________________________
> >>
> >> For help in using, subscribing, and unsubscribing to the discussion
> >> forums, please go to:
http://www.netdynamics.com/support/visitdevfor.html
> >>
> >> For dire need help, email: [EMAIL PROTECTED]
>
> _________________________________________________________________________
>
> For help in using, subscribing, and unsubscribing to the discussion
> forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
> For dire need help, email: [EMAIL PROTECTED]
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
