Re: [PHP4BETA] Re: Date/Time problem in ./ext/standard/datetime.c
| From: | Bob Denny | Date: | Sat, 26 Feb 2000 01:56:27 +0000 |
| Subject: | Re: [PHP4BETA] Re: Date/Time problem in ./ext/standard/datetime.c | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-11018@lists.php.net to get a copy of this message | ||
Adam --
> Fine, as long as it doesn't break the ability for old browsers to
> read cookies.
It's already an option (so called Y2K mode) to go to the newer
data/time format. Turning that off should be enough for the few who
want to be retro to that extent. But as Sascha and I have pointed out,
there is no room in the HTTP/1.1 spec for illegal formats. As it is,
the current "Y2K" format is simply illegal. The non-Y2K format is old,
deprecated but legal.
All I'm saying is that the new format should be the correct one. Leave
the old format there as is. My posted patch does this by altering the
Y2K format to be legal according to HTTP/1.1.
If you want to support the old Netscape Cookie format, and give the
PHP developer that choice when generating cookie strings, then it's my
opinion that you should decouple the date/time format used in cookies
from that used in the HTTP headers. I am really against putting those
old time formats in HTTP/1.0 headers, and if you're running on (or
doing nph type responses) with HTTP/1.1 then it is illegal.
At a minimum, you *must* fix the Y2K format to be legal, per HTTP/1.1.
-- Bob