Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:64454
Return-Path: <narf@bofh.bg>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 91112 invoked from network); 28 Dec 2012 03:42:14 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 28 Dec 2012 03:42:14 -0000
Authentication-Results: pb1.pair.com smtp.mail=narf@bofh.bg; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=narf@bofh.bg; 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:36013] helo=everlasting.spnet.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 9E/C2-59750-4151DD05 for <internals@lists.php.net>; Thu, 27 Dec 2012 22:42:13 -0500
Received: from web-1.orbitel.bg ([195.24.43.34])
	by everlasting.spnet.net with esmtp (Exim 4.72)
	(envelope-from <narf@bofh.bg>)
	id 1ToQpl-0002k6-2T; Fri, 28 Dec 2012 05:42:09 +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 05:42:02
	+0200
Message-ID: <20121228054202.4vzgnbu9s08kg4cc@mail.orbitel.bg>
Date: Fri, 28 Dec 2012 05:42:02 +0200
To: Sherif Ramadan <theanomaly.is@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
References: <20121210142818.9erzxulg08cwwck8@mail.orbitel.bg>
	<CAMUwpuSOW1=tht0j5VR3cS5_Meny4jorj-Dg5DaRR4F52YjAag@mail.gmail.com>
	<20121228042651.edrb8sz5cs4sgwwc@mail.orbitel.bg>
	<CAL+t6cF21RkJMk_ZRYjfu-Z37o7M=YfGRkR2LXu5YLQkog1Nsw@mail.gmail.com>
	<20121228045131.3g44jjlw8cc4sgk4@mail.orbitel.bg>
	<CAL+t6cGg9PF0Z=MHA_7eMh_oXfkjNkFzCBEHEs_9M3+he+LYkg@mail.gmail.com>
In-Reply-To: 	<CAL+t6cGg9PF0Z=MHA_7eMh_oXfkjNkFzCBEHEs_9M3+he+LYkg@mail.gmail.com>
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;1356666133;d9de7c0b;
Subject: Re: [PHP-DEV] Bug #23955: Cookie Max-Age attribute
From: narf@bofh.bg (Andrey Andreev)

Yes, of course - those are all valid points that you've listed.

Updated the RFC with the suggested additions. Hopefully it's more =20
easily understandable now. :)

Quoting Sherif Ramadan <theanomaly.is@gmail.com>:

> Well, even if it were obvious the RFC should be a technical specification
> of what's being introduced. Things should be stated and explained there as
> clearly as possible. At least so much so that people shouldn't have to
> guess about what is going to actually happen when they run certain code.
>
> For example, how are session cookies affected? What determines the actual
> delta? I would assume it's the determined by the Unix timestamp supplied t=
o
> setcookie? Should setting this attribute in the response headers be
> included automatically for session cookies? I would think it would, but I'=
m
> not certain since it's not mentioned.
>
> Other than some brief examples of usage and perhaps including those small
> details I think it's pretty clear and I like the idea :)
>
> Thanks for taking the time on that.