Richard Lynch wrote: > A cookie is sent BACK to the server after the server sends > it to the browser. Period. > > It's kind of like when you go to a movie, and you buy your > ticket from one person, and then you hand it to another, > and they hand it back, and then you have to be prepared to > show it to prove you aren't sitting through a second movie. > > Walking back out front to the ticket sales window, you don't > show them your ticket again... > > Maybe that's not such a good analogy...
You could "fix" it by explaining that no one should check to see whether you have a ticket before you've had a chance to buy one. The timing just doesn't make sense. Developers sometimes make the mistake of checking $_COOKIE (a convenient representation of the Cookie header from the previous request) before a Set-Cookie header has been sent to the browser. The browser can't return something it has never received. Chris -- Chris Shiflett http://shiflett.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
