Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64456 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 5047 invoked from network); 28 Dec 2012 07:13:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Dec 2012 07:13:55 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 173.203.6.147 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 173.203.6.147 smtp147.ord.emailsrvr.com Linux 2.6 Received: from [173.203.6.147] ([173.203.6.147:57004] helo=smtp147.ord.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/E3-59750-FA64DD05 for ; Fri, 28 Dec 2012 02:13:54 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp15.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 30BDA27008A; Fri, 28 Dec 2012 02:13:49 -0500 (EST) X-Virus-Scanned: OK Received: by smtp15.relay.ord1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id BBA86270083; Fri, 28 Dec 2012 02:13:48 -0500 (EST) Message-ID: <50DD46AB.70601@sugarcrm.com> Date: Thu, 27 Dec 2012 23:13:47 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Andrey Andreev CC: Sherif Ramadan , PHP Internals References: <20121210142818.9erzxulg08cwwck8@mail.orbitel.bg> <20121228042651.edrb8sz5cs4sgwwc@mail.orbitel.bg> <20121228045131.3g44jjlw8cc4sgk4@mail.orbitel.bg> In-Reply-To: <20121228045131.3g44jjlw8cc4sgk4@mail.orbitel.bg> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Bug #23955: Cookie Max-Age attribute From: smalyshev@sugarcrm.com (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. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227