Question: When you write a cookie with an expiration date in the future to a particular machine, the cookie never seem to be set. The technique usually works with other computers, and you have checked that the time on the machine corresponds to the time on the server within a reasonable margin by verifying the date reported by the operating system on the client computer’s desktop. The browser on the client machine seems to otherwise work fine on most other websites. What could be likely causes of this problem? (Choose 2)
AThe browser’s binaries are corrupt
BThe client machine’s time zone is not set properly
CThe user has a virus-scanning program that is blocking all secure cookie
DThe browser is set to refuse all cookies
EThe cookie uses characters that are discarded all data from your server
Note: Answers A and D both describe likely causes of this type of problem and warrant further investigation on your part. Since the browser seems to work fine, it’s unlikely that its binaries have suffered corruption such that only your site has stopped working, and virus scanning programs do not normally stop secure cookies selectively (although some block all cookies). On the other hand, the browser might have been explicitly set to refuse all cookies, which is probably the first source of trouble you should check for. By the same token, the computer’s time zone might have been set incorrectly and, since cookie expiration dates are
coordinated through GMT, cause the cookie to expire as soon as it was set and never be returned to your scripts.