Who Stole the Cookie?
You may find that your cookie hasn’t been set (IsDefined) at a certain point in your page sequence when under normal conditions it should have been (you think). This is usually because your visitor has refused the cookie, but it could be that he or she is using an ancient browser that doesn’t support cookies. A third possibility is that your visitor has bookmarked one of your pages and the cookie he or she once had has expired. I can’t suggest what you should do in all cases for all Web sites, but you should be aware of these possibilities and try to program for them. Unfortunately, it probably won’t be possible to determine why the cookie hasn’t been set. Common Cookie Bugs You need to know that the browser uses information in the HTTP headers (which you and your users normally never see) to set the cookie. Knowing this will help avoid two common bugs. Bug 1: You cannot test for the cookie being set on the same page as the page containing the CFCOOKIE. Whatever your IsDefined test ret