That really won't work. The problem with it is that during the execution of
the CFM template, the cookies will exist. They are only refused after the
HTTP headers are returned to the client. In other words, the cookies will
be defined as long as the template setting them is executing.
A better solution would be to set the cookies on a initially loaded page and
use a client side redirect to send the user to the test template. That way
the client will get the headers setting the cookies, and a new request will
be generated for the test template. If the cookies exist there, then the
client accepts cookies.
Hope this helps.
Russel
> -----Original Message-----
> From: Jennifer [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 24, 2001 1:43 PM
> To: CF-Talk
> Subject: Re: cookies
>
>
> At 05:57 PM 7/24/2001 +0100, you wrote:
> >Do you know how to use CF to check if a browser will accept cookies?
>
> Try setting one and run isDefined() on it. If it's defined, cookies are
> enabled. If not, no cookies.
>
> Just remember that some people have their browser set to warn before
> accepting a cookie.
>
> Now available in a San Francisco Bay Area near you!
> http://63.74.114.11/mr_urc/index.cfm
> http://63.74.114.11/mr_urc/resume.cfm
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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