Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:64451 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84034 invoked from network); 28 Dec 2012 02:37:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Dec 2012 02:37:04 -0000 Authentication-Results: pb1.pair.com header.from=theanomaly.is@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=theanomaly.is@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) X-PHP-List-Original-Sender: theanomaly.is@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-wg0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:65097] helo=mail-wg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 18/B1-59750-FC50DD05 for ; Thu, 27 Dec 2012 21:37:03 -0500 Received: by mail-wg0-f42.google.com with SMTP id dr1so4011993wgb.5 for ; Thu, 27 Dec 2012 18:37:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7ZDSeYNvVzdN8vMZJQqwqoShK6+MUF3aNtxTJMRRmIA=; b=JlzQ97Ikca12ZOv5KO+Ea9BXAMIbqNUByDlO3ty9gBb7BuyN6x+BvimwXt7JWUUXKs BRPIz0aMXYcmehDYpHhYSuZPe3C0W2S2cumVhR8jAxmiyUXx0i6E+t6RW2UJ65XEZ4Z4 RcJ+OJRF0nyftjJhee5NAefrWA3Cf5lbDQTBDqsQENLqE9nN5Y58Hn0PV92LMn1BEOO8 tGbU5+YSkpdaa9KmfgHkltQyqcRzzKMvrNX4zP+vKEaj9nA5EBiHdLVs1Gw1r+zsG5yd MI4cOxfGnW6c98Z4mKzqbAwk1WJldBXAX8933/m8UvPTcwJ1Od7k6ePOqcj3Z9BdN2PG 4uFQ== MIME-Version: 1.0 Received: by 10.180.82.69 with SMTP id g5mr50987644wiy.21.1356662220593; Thu, 27 Dec 2012 18:37:00 -0800 (PST) Received: by 10.227.43.19 with HTTP; Thu, 27 Dec 2012 18:37:00 -0800 (PST) In-Reply-To: <20121228042651.edrb8sz5cs4sgwwc@mail.orbitel.bg> References: <20121210142818.9erzxulg08cwwck8@mail.orbitel.bg> <20121228042651.edrb8sz5cs4sgwwc@mail.orbitel.bg> Date: Thu, 27 Dec 2012 21:37:00 -0500 Message-ID: To: Andrey Andreev Cc: PHP Internals Content-Type: multipart/alternative; boundary=f46d0442838abd1be804d1e0892e Subject: Re: [PHP-DEV] Bug #23955: Cookie Max-Age attribute From: theanomaly.is@gmail.com (Sherif Ramadan) --f46d0442838abd1be804d1e0892e Content-Type: text/plain; charset=ISO-8859-1 On Thu, Dec 27, 2012 at 9:26 PM, Andrey Andreev wrote: > At last, I was able to write an RFC about this: > > https://wiki.php.net/rfc/**cookie_max-age > > - Andrey > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > There's no mention in the RFC of how the functionality will work in PHP. Is it possible to add example code of how it is to be used based on this implementation? 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. --f46d0442838abd1be804d1e0892e--