Thanks for the responses. Lots of good food for thought. The reason that I initially went with database-bound client vars was due to an early CFMX bug whereby cookies weren't getting set correctly in all browsers. I believe it was fixed in CFMX 6.1, but since everything was smoothly running on the setup at the time didn't bother changing it then.
I made the change back to client cookies today, and it appears to be working largely as intended. However, cookies still seem to behave erratically. For example, I find a client var set (setdomaincookies=yes) from a page at "domain.com/login.cfm" is usually also found on a page at "www.domain.com/login.cfm" in IE, but not in Firefox. Firefox isn't acknowledging "www.domain.com" and "domain.com" as equivalent for purposes of client cookies. To make things even more confusing, if I delete a client variable in www.domain.com/test.cfm then re-create it in www.domain.com/test2.cfm, sometimes IE doesn't even acknowledge that it has been set. IE seems to get confused and will refuse to set the cookie correctly until it's either rebooted or you use "clear all cookies" in the browser. I honestly am not sure what the deal is, but I'm finding it very frustrating trying to get multiple browsers to react consistently to "cookie" client variables. Right now it seems to me that client variables (type=cookie), when set, do one of three things in the same browser, depending on how the browser is feeling at the time: - cli var gets set correctly, and is acknowledged under *.domain.com - cli var gets set correctly, but is only acknowledged under current.domain.com - doesn't get set at all. browser entirely ignores it. It tends to exhibit this behavior if the client variable was just recently deleted and then re-established (such as a login after a logout). These behaviors disappear the INSTANT I turn client storage from "cookie" to "database". If anyone has any insight into what the problem may be, please let me know. As I'm on update 6.1, I didn't think I needed the "setdomaincookies" hot fix, which is listed on the MM site as an MX 6.0 fix. Whose fault is this erratic behavior... CF's, IE's, or mine? Thanks Terry ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:205988 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=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
