> Hello, > Are you using IE7? I had some code that was acting funny when run > locally but then was fine on the production server. Looking at the > code you posted, Why are you using cookies to track the user when your > code is using sessions? > Chris
In the latest error event, the agent was reported as: Browser:Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) I suppose it could be our tracking javascript in combination with IE 5, though I still am unsure how it could be causing a variable in cold fusion to become undefined after clearing having been defined.. Unless it is possible that a cookie could be sent with a name but somehow have an undefined value? But I would think if that were the case, then the error would be thrown earlier in the script when the cookie is referenced. As for why we are tracking the user in this manner, there are several reasons: 1) Every reliable CF implementation of persistant session or client variables requires cookies. We cannot require cookies to be enabled for our tracking to work properly, so another method had to be employed. 2) We require the session to track across multiple domains (not subdomains, but domains) One of our domains has a dash, the other does not; we require the same session to track across both domains reliably. This required a custom tracking method. The original (broken) tracking implementation relied soley on session variables, and broke whenever the user turned off cookies. Even worse, for those users that had cookies turned off, a new session identifier was generated each time they clicked something on the website, thus skewing our user counts, having dozens and dozens of "dead" sessions still counted as "live" sessions, which was unacceptable. The application definition is still there, because we use an application-scoped structure to store tracking info, and session variables are still enabled to make it easier to generate reliably unique session identifiers (CFTOKEN, etc) for our custom tracking implementation. I have considered scrapping the session variables in favor of an application-scoped key generator, but I assume that the session identifier generator provided by cold fusion can reliably provide guaranteed unique identifiers, which a custom implementation could not do without using a database or some other server-stored value. (persistant after server restart, as we want guaranteed completely unique identifiers) -- Pat ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268478 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
