Then call a page with this
<cfoutput>
<p>cfid=#cfid#</p>
<p>cftoken=#cftoken#</p>
</cfoutput>
the values will be shown...however if you call the page again the values will change because the browser has been told not to store them and the server sends new values.
you can't really check on the initial page, you have to see if the value has changed on subsequent calls. So one could identify the user using his IP address and store the IP address, cfid and cftoken in an application variable (a structure would be ideal using the IP as the key), then on the next page compare the cfid & cftoken stored in the application variable with the actual values on the page. If they are the same cookies are enabled.
Of course relying on the IP address as the primary identification is not reliable because of proxy servers so the above method will not work 100%.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
