Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64452 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85973 invoked from network); 28 Dec 2012 02:51:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Dec 2012 02:51:41 -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:50804] helo=everlasting.spnet.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2E/02-59750-A390DD05 for ; Thu, 27 Dec 2012 21:51:40 -0500 Received: from web-1.orbitel.bg ([195.24.43.34]) by everlasting.spnet.net with esmtp (Exim 4.72) (envelope-from ) id 1ToQ2p-0008Gw-GH; Fri, 28 Dec 2012 04:51:35 +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 04:51:31 +0200 Message-ID: <20121228045131.3g44jjlw8cc4sgk4@mail.orbitel.bg> Date: Fri, 28 Dec 2012 04:51:31 +0200 To: Sherif Ramadan Cc: PHP Internals References: <20121210142818.9erzxulg08cwwck8@mail.orbitel.bg> <20121228042651.edrb8sz5cs4sgwwc@mail.orbitel.bg> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; 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;1356663100;2e395f98; Subject: Re: [PHP-DEV] Bug #23955: Cookie Max-Age attribute From: narf@bofh.bg (Andrey Andreev) Quoting Sherif Ramadan : > There's no mention in the RFC of how the functionality will work in PHP. I= s > it possible to add example code of how it is to be used based on this > implementation? "Max-Age" would simply be added to all Set-Cookie headers, after the =20 "Expires" attribute. I thought that was obvious, but I'll make sure to =20 add a few examples to make it clearer. > What BC breaks it introduced (if any)? Can there be an > option to use both Max-Age and Expires cookie attributes with the > introduced changes? How does the user know which attribute is being set? > None of this information seems to be in the RFC. This is all (briefly) described under the "Technical details and =20 considerations" section - both attributes should be sent and no side =20 effects and/or breaking changes are expected. As for how a user would know it - just like with the current cookies =20 being sent (either via setcookie() or by ext/session), by looking at =20 their Set-Cookie HTTP headers.