The idletimeout is part of the cflogin tag and it's separate from the session timeout. If it's longer than or the same as the session timeout it will expire with the session in this case as the loginstorage specified in the OP was "session." If it's shorter than the session timeout, the login will expire even though the session doesn't.
mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ 2009/5/15 Ian Skinner <[email protected]>: > > Brian Bradley wrote: >> To make sure that I have this down (I have to present this today). Using >> cflogin, the idletimeout is 30 minutes so IE will keep the user logged in >> for the 30 minutes or whatever time I adjust it to. I can set a cookie that >> will keep the user logged in indefinitely with if statements, etc. > No that is not it. The idletimeout means that ColdFusion will keep a > session alive for 30 minutes waiting for another request to come in with > the session identifier that is usually stored in a cookie. If no new > request comes in in that time period the session will be deleted and > ColdFusion will not return the data if the session identifier comes in > at a later time. The session cookies in IE or any browser can actually > be set to never expire, but if a request is not sent to the ColdFusion > server in the 30 minute window the session state on the server will be ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:322561 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
