RE: [PHP-DEV] PHP 4.0 Bug #5596: SetCookie isn't compliant

It doesn't surprise me that they would change it, probably y2k concerns, however 2 or 4 digit year, doesn't matter as far was WAP is concerned actually. The only problem comes with the -'s, both examples, new and the original one, do have the dashes and will work on WAP. But, the way PHP is outputting them (Wdy, DD Mon YYYY HH:MM:SS GMT) will not work on WAP. From our testing with WAP, the fully spelled out day works, 2 or 4 digit years work, but in any instance if the format is missing the dashes the cookie will not be set on a wireless web application. I believe that adding the dashes won't break any existing browsers to add them in since published specs call for them. Brad Schuetz -= brad@cimmeria.com =- -----Original Message----- From: Rasmus Lerdorf [mailto:rasmus@php.net] Sent: Thursday, July 13, 2000 5:47 PM To: brad@cimmeria.com Cc: php-dev@lists.php.net Subject: Re: [PHP-DEV] PHP 4.0 Bug #5596: SetCookie isn't compliant > In developing a WML based system for WAP (Wireless Web Phones) we discovered a bug with the SetCookie function. > > The format according to early specifications by Netscape (http://home.netscape.com/newsref/std/cookie_spec.html) which are all in the RFC's (linked from that page), which have been adopted by most as the standard, show the format as: > > Wdy, DD-Mon-YYYY HH:MM:SS GMT Actually, this is not the case. The original spec had this format: Wednesday, 09-Nov-99 23:12:40 GMT They went back and changed some of the wording, but the very first example in the very URL you quoted is: Set-Cookie: CUSTOMER=WILE_E_COYOTE; path=/; expires=Wednesday, 09-Nov-99 23:12:40 GMT Note the 2-digit year as well. -Rasmus