--- Curt Zirzow <[EMAIL PROTECTED]> wrote: > > Now, when a browser sends this, it will be something like this: > > > > Cookie: coach_access[login_id]=coach > > A cookie name can only be a HTTP/1.1 tolken as defined in rfc2109:
Well, this isn't the case. You see, neither RFC 2109 nor RFC 2965 are perfectly in synchronization with the implementation of cookies. The best specification to reference is Netscape's original, because this is what the browsers adhered to originally, and little has changed since. As mentioned in the PHP manual, the specification can be found here: http://wp.netscape.com/newsref/std/cookie_spec.html Also, if you will run a quick test, you will observe the behavior I described in my earlier message. I was not making it up. :-) Hope that helps. Chris ===== Become a better Web developer with the HTTP Developer's Handbook http://httphandbook.org/ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
