| Subject: | Re: Logging out issues |
|---|---|
| From: | GArlington <garlington@xxxxxxxxxxxxx> |
| Date: | Wed, 30 Jul 2008 03:31:26 -0700 (PDT) |
| Newsgroups: | macromedia.coldfusion.getting_started |
On Jul 29, 5:25 pm, "JordonShaw" <webforumsu...@xxxxxxxxxxxxxx> wrote: > I'm wondering if maybe my application script has anything to do with it. > It looks like you are better qualified then anybody else to answer your questions, few people asked you to post your LOGIN and LOGOUT code and you decide that the problem is in your Application.cfm So maybe you do not even need to ask your question here? SESSIONTIMEOUT in above code should be short because it allows the SERVER (CF) to release resources when session is inactive (browser window close has that effect) for a long time (longer then SESSIONTIMEOUT), if session is active each request will reset the counter so it will leave another SESSIONTIMEOUT time before the session is killed and resources are released. So, with normal browsing 20 mins is widely accepted to be about right, you can increase that to about an HOUR (maximum) if you have a lot of big documents that can only be read on-line, but you should NEVER use SESSIONTIMEOUT as long as yours = 1 DAY. WHY??? Your LOGOUT code should clear the session structure effectively killing the session... |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Changing CF runtime user, Daverms |
|---|---|
| Next by Date: | application.cfc / cflogin prevents page display, wltiii_2 |
| Previous by Thread: | Re: Logging out issues, JordonShaw |
| Next by Thread: | Re: Logging out issues, BKBK |
| Indexes: | [Date] [Thread] [Top] [All Lists] |