I'm not getting back into it again, but there are further problems when  
you use idletimeout, sesion variables that are set in a <cflogin> block  
and deleted during <cflogout> and server authentication.

-Patti
On Thursday, March 20, 2003, at 11:06  AM, Raymond Camden wrote:

> FYI, this is part of a 'feature' as well. The use of cflogin.* makes it
> possible for your login to work over clusters. So - it's good and bad.
> ;)
>
> However, if you use
>
> <cfif not isDefined("session.somemarker")>
>       <cflogout>
> </cfif>
>
> It _should_ work correctly. (If you sync up cflogin timeout and session
> timeouts.) I haven't tested it though. You may have to delete the
> cflogin cookie as well.
>
> =======================================================================
> Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc
> Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia)
>
> Email    : [EMAIL PROTECTED]
> Blog     : www.camdenfamily.com/morpheus/blog
> Yahoo IM : morpheus
>
> "My ally is the Force, and a powerful ally it is." - Yoda
>
>> -----Original Message-----
>> From: Patricia G. L. Hall [mailto:[EMAIL PROTECTED]
>> Sent: Thursday, March 20, 2003 8:58 AM
>> To: CF-Talk
>> Subject: Re: Application Security using cflogin and cfloginuser
>>
>>
>> I knew it.
>>
>> On Monday, March 17, 2003, at 02:04  PM, Raymond Camden wrote:
>>
>>> 1) If you use cflogin.* to check for logins, idleTimeout ceases to
>>> function.
>>
>>
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to