Well, as far as I know, You should check the session
variable first. If they don't exist(session has
expired) then use the cflogout tag to logout the user
and redirect him to the login page or where ever you
want.
For session expiration issue(as you said you need to
expire the session when the browser is closed or when
seesion timeout is encountered) consider using browser
only cookies because if you use persistent cookies,
they don't get expired when the browser is closed(as
far as I have experienced). The following code shows
how to use browser only cookies.

<cfapplication name="ABCD" SESSIONMANAGEMENT="YES"
clientmanagement="No" setClientCookies = "No"
sessionTimeout = #CreateTimeSpan(0, 0, 20, 0)#>

<!--- CF will not set the client cookies
automatically, so
set them manually as per-session cookies --->
<CFLOCK SCOPE="SESSION" TYPE="READONLY" TIMEOUT="5">
<CFCOOKIE NAME="CFID" VALUE="#SESSION.CFID#">
<CFCOOKIE NAME="CFTOKEN" VALUE="#SESSION.CFTOKEN#">
</CFLOCK>

Let me know if you need more help.
Regards,
Kamran

need to check the session variables rather than
cflogin f
--- [EMAIL PROTECTED] wrote:
> Ok, new issue. I'm using the CFLogin framework. I'm
> also using some session
> variables. How do I ensure that they both timeout at
> the same time? Or, is
> there a way to have the session variables only
> expire when the browser is
> closed or if a cfapplication tag with a
> sessiontimeout of 0 is encountered?
> The problem is that the session variables contain
> things like the name to
> be displayed, stylesheet to use, etc., and the user
> encouters cold fusion
> errors when they timeout because those references
> are encountered before
> the cflogin tag, which may not  have expired when
> the session variables
> did.
>
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to