Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64458 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 48963 invoked from network); 28 Dec 2012 16:15:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Dec 2012 16:15:23 -0000 Authentication-Results: pb1.pair.com header.from=narf@bofh.bg; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=narf@bofh.bg; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain bofh.bg from 212.50.12.79 cause and error) X-PHP-List-Original-Sender: narf@bofh.bg X-Host-Fingerprint: 212.50.12.79 everlasting.spnet.net Linux 2.6 Received: from [212.50.12.79] ([212.50.12.79:34293] helo=everlasting.spnet.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A3/94-15058-995CDD05 for ; Fri, 28 Dec 2012 11:15:22 -0500 Received: from web-1.orbitel.bg ([195.24.43.34]) by everlasting.spnet.net with esmtp (Exim 4.72) (envelope-from ) id 1Tocac-0005c7-9Z; Fri, 28 Dec 2012 18:15:18 +0200 Received: from core.devilix.net (core.devilix.net [87.97.157.170]) by mail.orbitel.bg (Horde MIME library) with HTTP; Fri, 28 Dec 2012 18:15:14 +0200 Message-ID: <20121228181514.utdov86o3ocksgck@mail.orbitel.bg> Date: Fri, 28 Dec 2012 18:15:14 +0200 To: Stas Malyshev Cc: PHP Internals References: <20121210142818.9erzxulg08cwwck8@mail.orbitel.bg> <20121228042651.edrb8sz5cs4sgwwc@mail.orbitel.bg> <20121228045131.3g44jjlw8cc4sgk4@mail.orbitel.bg> <50DD46AB.70601@sugarcrm.com> In-Reply-To: <50DD46AB.70601@sugarcrm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.6) X-Originating-IP: 87.97.157.170 X-Originating-User: narf@bofh.bg X-bounce-key: spectrumnets-1;narf@bofh.bg;1356711322;b4972408; Subject: Re: [PHP-DEV] Bug #23955: Cookie Max-Age attribute From: narf@bofh.bg (Andrey Andreev) It is briefly noted in the RFC (mine, not 6265) that negative values =20 and 0 have the same effect. It's practically irrelevant which one is =20 sent. My original commit actually did checks for negative values and sent =20 zeros instead of them, but then somebody on github pointed out that =20 they are legal, so I removed that logic. If not anything else, it =20 saves a few lines of code. - Andrey Quoting Stas Malyshev : > Hi! > >> "Max-Age" would simply be added to all Set-Cookie headers, after the >> "Expires" attribute. I thought that was obvious, but I'll make sure to >> add a few examples to make it clearer. > > I think it makes sense, only note is that it makes no sense to set > Max-Age to any negative number, especially as RFC 6265 treats all > negative values and 0 as the same: > > If delta-seconds is less than or equal to zero (0), let expiry-time be > the earliest representable date and time. Otherwise, let the > expiry-time be the current date and time plus delta-seconds seconds.