Make sure your mx server isn't using a uuid for cfid/cftoken... I
believe when this is the case it only uses the one variable, and so
your cfif statement would return false when either one of the
isdefined() returns false and your cookies wouldn't get reset to log
the user out when the browser closes.
That's the only thing that comes to mind for me at the moment.
hth
s. isaac dealey 214-823-9345
team macromedia volunteer http://www.macromedia.com/go/team
chief architect, tapestry cms http://products.turnkey.to
onTap is open source http://www.turnkey.to/ontap
> I am porting our application to MX 6.1. We are not
> refactoring anything yet,
> simply re-deploying. However, I decided to redo the login
> mechanism using
> <cflogin> architecture.
> In my Application.cfm I have:
> <cfif not isdefined("session.loggedin")>
> <cfinclude template="_login.cfm">
> </cfif>
> _login.cfm, among other things, instantiates
> session.loggedin var.
> What I am experience is that upon session expiration the
> above <cfif> block
> in Application.cfm doesn't get prevent the application to
> execute further.
> What am I missing?
> We are not using J2EE session variables, but I have this
> in my
> application.cfm:
> <cfif isdefined('cookie.cfid') and
> isdefined('cookie.cftoken')>
> <cfset localCFID = cookie.cfid>
> <cfset localCFToken = cookie.CFTOKEN>
> <cfcookie name = "CFID" value = "#localCFID#">
> <cfcookie name = "CFTOKEN" value = "#localCFTOKEN#">
> </cfif>
> Thanks for any tips!
> Stas
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
