that's the inherent problem with what you are trying to do....you are trying to validate something that is client side, using a server side technology :)
what you could do, is put the cookie check on the previous page, a simple non-sense cookie that just tests...then, on the page you want to set your real cookie..you could say "hey you don't have cookies turned on, get em on now!!!" but that's still a two page setup tony weeg uncertified advanced cold fusion developer tony at navtrak dot net www.navtrak.net office 410.548.2337 fax 410.860.2337 -----Original Message----- From: Gabriel Robichaud [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 3:17 PM To: CF-Talk Subject: Re: cookie detection I guess i should have been more clear in my question... doing it in 2 pages is what i wanted to avoid. It would be nice if i could just test to see if the user has cookies enabled and then do treatment accordingly. That would let me do something in Application.cfm... but I guess i'll handle it in my header file. thank you philip for your answer. Gabriel Philip Arnold wrote: >>I would think, just set it, then try to read it (if it doesnt >>exist) it's disabled ;) hehe > > > But you HAVE to do it over 2 pages > > If you try to set one and then check it on the same page, it hasn't > had a chance to get to the browser, so it's always set... > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq 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 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
