RE: Session not being killed on close of browser
Just to make things more interesting, the same code works in another site we have built. The only difference is that the first page on the problem site, index.cfm, cflocates you to another page. Could this redirect be the problem? We've had it as a javascript redirect to see if that helped, but still no joy. I know client vars aren't effected by redirects, but the swap to a cookie could be causing a problem. Anyone have any thoughts on this? Ade -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: 31 July 2002 18:17 To: CF-Talk Subject: RE: Session not being killed on close of browser Matthew, Smiles. (By the way, I didn't take offense at your message at all--on the contrary, I am glad for the correction.) It's funny, though, it makes me think that I'd almost like there to be ratings on the list: each person has to go through some rigorous testing regime where they get a rating of zero, one, or two. This rating would correspond to the number of grains of salt with which replies from the person in question should be taken. That way, pseudo-newbies like me (who would have a two-grain rating) could post answers without worrying that we're causing more problems than we're solving! :) Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:48 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Dude, no need to apologize, I was just trying to help same as you were. No worries. The best part of this list is that we have many great minds to pick when solving a problem. At least you replied and tried to help, ya know? : ) Matthew P. Smith Web Developer, Object Oriented Naval Education Training Professional Development Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:26 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATION NAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The
RE: Session not being killed on close of browser
are you on mx? -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 01, 2002 5:35 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Just to make things more interesting, the same code works in another site we have built. The only difference is that the first page on the problem site, index.cfm, cflocates you to another page. Could this redirect be the problem? We've had it as a javascript redirect to see if that helped, but still no joy. I know client vars aren't effected by redirects, but the swap to a cookie could be causing a problem. Anyone have any thoughts on this? Ade -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: 31 July 2002 18:17 To: CF-Talk Subject: RE: Session not being killed on close of browser Matthew, Smiles. (By the way, I didn't take offense at your message at all--on the contrary, I am glad for the correction.) It's funny, though, it makes me think that I'd almost like there to be ratings on the list: each person has to go through some rigorous testing regime where they get a rating of zero, one, or two. This rating would correspond to the number of grains of salt with which replies from the person in question should be taken. That way, pseudo-newbies like me (who would have a two-grain rating) could post answers without worrying that we're causing more problems than we're solving! :) Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:48 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Dude, no need to apologize, I was just trying to help same as you were. No worries. The best part of this list is that we have many great minds to pick when solving a problem. At least you replied and tried to help, ya know? : ) Matthew P. Smith Web Developer, Object Oriented Naval Education Training Professional Development Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:26 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATION NAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of
RE: Session not being killed on close of browser
Yup, and I've just read Brain J LeRoux's post which may have some standing. Maybe it's the mix of MX and IE6? Ade -Original Message- From: Tangorre, Michael [mailto:[EMAIL PROTECTED]] Sent: 01 August 2002 11:57 To: CF-Talk Subject: RE: Session not being killed on close of browser are you on mx? -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 01, 2002 5:35 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Just to make things more interesting, the same code works in another site we have built. The only difference is that the first page on the problem site, index.cfm, cflocates you to another page. Could this redirect be the problem? We've had it as a javascript redirect to see if that helped, but still no joy. I know client vars aren't effected by redirects, but the swap to a cookie could be causing a problem. Anyone have any thoughts on this? Ade -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: 31 July 2002 18:17 To: CF-Talk Subject: RE: Session not being killed on close of browser Matthew, Smiles. (By the way, I didn't take offense at your message at all--on the contrary, I am glad for the correction.) It's funny, though, it makes me think that I'd almost like there to be ratings on the list: each person has to go through some rigorous testing regime where they get a rating of zero, one, or two. This rating would correspond to the number of grains of salt with which replies from the person in question should be taken. That way, pseudo-newbies like me (who would have a two-grain rating) could post answers without worrying that we're causing more problems than we're solving! :) Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:48 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Dude, no need to apologize, I was just trying to help same as you were. No worries. The best part of this list is that we have many great minds to pick when solving a problem. At least you replied and tried to help, ya know? : ) Matthew P. Smith Web Developer, Object Oriented Naval Education Training Professional Development Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:26 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATION NAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening
RE: Session not being killed on close of browser
Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATION NAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s) . Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0) 20 7387 8890 __ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: Session not being killed on close of browser
I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATIONNAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s) . Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0) 20 7387 8890 __ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: Session not being killed on close of browser
Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATIONNAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s) . Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0) 20 7387 8890 __ 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 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: Session not being killed on close of browser
Dude, no need to apologize, I was just trying to help same as you were. No worries. The best part of this list is that we have many great minds to pick when solving a problem. At least you replied and tried to help, ya know? : ) Matthew P. Smith Web Developer, Object Oriented Naval Education Training Professional Development Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:26 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATION NAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s) . Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0) 20 7387 8890 __ 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 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: Session not being killed on close of browser
In Advanced Privacy Settings I have checked Override automatic cookie handling, accepted first and third party cookies, and checked the box marked Always allow session cookies, but still no joy. Has anyone else had trouble with it not working as expected? Ade -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: 31 July 2002 16:26 To: CF-Talk Subject: RE: Session not being killed on close of browser Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATIONNAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s) . Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0) 20 7387 8890 __ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
RE: Session not being killed on close of browser
Matthew, Smiles. (By the way, I didn't take offense at your message at all--on the contrary, I am glad for the correction.) It's funny, though, it makes me think that I'd almost like there to be ratings on the list: each person has to go through some rigorous testing regime where they get a rating of zero, one, or two. This rating would correspond to the number of grains of salt with which replies from the person in question should be taken. That way, pseudo-newbies like me (who would have a two-grain rating) could post answers without worrying that we're causing more problems than we're solving! :) Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:48 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Dude, no need to apologize, I was just trying to help same as you were. No worries. The best part of this list is that we have many great minds to pick when solving a problem. At least you replied and tried to help, ya know? : ) Matthew P. Smith Web Developer, Object Oriented Naval Education Training Professional Development Technology Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:26 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Oops! I'm sorry. I should have read the documentation before sending that answer. Omitting the EXPIRES attribute makes it so that the cookie stays open only as long as the browser is open. That's exactly what Adrian was shooting for. Okay. Now that I understand that, I can only suggest that you look at the security settings in the Internet Options. I know that the options there have different entries for cookies and per-session cookies, so that you can enable/disable them independently. Perhaps your version of the browser handles this differently? It seems crazy, but maybe it's forcing the per-session cookies to be written to the machine somehow? Again, sorry about the shooting-from-the-hip silly answer. Matthieu -Original Message- From: Smith, Matthew P -CONT(DYN) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 11:13 AM To: CF-Talk Subject: RE: Session not being killed on close of browser I thought that by omitting it, the default value sent WAS now? Matt -Original Message- From: Cornillon, Matthieu [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 10:01 AM To: CF-Talk Subject: RE: Session not being killed on close of browser Adrian, Is that CFIF block supposed to kill the cookies, thus detaching the session? If so, the only thing I can think of is to specify, in the CFCOOKIE statements, the parameter expires=NOW. Perhaps omitting it sends a value which some browsers interpret differently than others? Matthieu -Original Message- From: Adrian Lynch [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 31, 2002 7:49 AM To: CF-Talk Subject: Session not being killed on close of browser Sorry for bring up this old chestnut, I've searched the web, the archives, under the sofa and still can't find an answer. I'm using this code in Application.cfm.. CFAPPLICATION NAME=myApp CLIENTMANAGEMENT=Yes SESSIONMANAGEMENT=Yes APPLICATIONTIMEOUT=#CreateTimeSpan(1,0,0,0)# CLIENTSTORAGE=myApp_clientData SETCLIENTCOOKIES=Yes cfif IsDefined(Cookie.CFID) AND IsDefined(Cookie.CFTOKEN) cfset cfid_local = Cookie.CFID cfset cftoken_local = Cookie.CFTOKEN cfcookie name=CFID value=#cfid_local# cfcookie name=CFTOKEN value=#cftoken_local# /cfif which I understand, and which works for some people in my office. But not for me. I have IE6 where as they run IE5.* I've closed ALL my browsers, leaving it a long time before opening afresh, and even loggin in this morning I had the same session running. We're running MX on NT if that makes a difference. Could it be the browser is the problem? Is there anything wrong with the code? Has anyone coming across this before? Are there any pitfalls to be aware of in the rest of the code in the site? Any thought would be nice? Adrian Lynch Thoughtbubble Ltd -- United Kingdom http://www.thoughtbubble.net Ph: +44 (0) 20 7387 8890 -- The information in this email and in any attachments is confidential and intended solely for the attention and use of the named addressee(s) . Any views or opinions presented are solely those of the author and do not necessarily represent those of Thoughtbubble. This information may be subject to legal, professional or other privilege and further distribution of it is strictly prohibited without our authority. If you are not the intended recipient, you are not authorised to disclose, copy, distribute, or retain this message. Please notify us on +44 (0) 20 7387 8890
