On Mon, 28 Feb 2005 18:41:15 -0400, Larry White wrote: > That's correct. Only the app name, thus sessionid, should change. > The CFID/CFTOKEN should not. That's why I was asking if there is any > CFCOOKIE tags in the applications that would affect them. It's not > necessarily the application.cfm files that are causing this.
Holy crap. I was told we don't use cookies, and I actually believed it. It didn't occur to me that we'd manipulate the CF cookies. I decided to do a search fo "cookie" through all of our client apps, and it turns out that on every different client's index.cfm page (this app has a lot of common code for each client, but each client also has their own directory with its own index.cfm), we expire the two cookies: cfid and cftoken. And there we have it. (I assume -- I'll have to do some tests, of course) Oh my God. Thank you SO much (both to you and to Adrian). Now I get to ask the original developers why they do that cookie expiration to see if I can get rid of it. Seems like clearing out the session instead of expiring the cookies would accomplish what they're trying to do without touching the other application's session. Scott -- ----------------------------------------- Scott Brady http://www.scottbrady.net/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196943 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
