Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85254
Return-Path: <yohgaki@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 92801 invoked from network); 20 Mar 2015 00:51:10 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 Mar 2015 00:51:10 -0000
Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.50 as permitted sender)
X-PHP-List-Original-Sender: yohgaki@gmail.com
X-Host-Fingerprint: 209.85.218.50 mail-oi0-f50.google.com  
Received: from [209.85.218.50] ([209.85.218.50:36552] helo=mail-oi0-f50.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id A8/23-25408-CFE6B055 for <internals@lists.php.net>; Thu, 19 Mar 2015 19:51:09 -0500
Received: by oigv203 with SMTP id v203so79555148oig.3
        for <internals@lists.php.net>; Thu, 19 Mar 2015 17:51:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:content-type;
        bh=Uj45bw3SSFkCqZqyTvC8J0CNGlUtVm2U4To4ZyfEyao=;
        b=WUI53pETrmS+xkySkUZjmwiUP4Z0xGGNnPHFgVcPbhNaZ7VsR/PLxHlWvJEp+ZcIl+
         vd6Lm9pb2BWcCDtD9H2LbVkQIEZh71ZTubN6rbY+i2i1Nz7s/1TOn4s+1XP+1BTxiWBD
         e1gYvy9r0sjtxSoTwlQKe91oRH+b679MmOGW9iXwH7zoKCxMAqcam7a0hv0D3ZgrDlbr
         2Ip1xlSt3/zQCm/mqoZo0XhpRQhJZbQF0fJw4/uSxwjOsf4rPU275eysHORkOGBQbsjS
         YNsWwQuymDK1MeAXruoHMlODdsaCjdA6354ZIN1+zVEncP5cX6v1dTS7NvgJonAbCBvA
         dp1Q==
X-Received: by 10.60.115.99 with SMTP id jn3mr64360105oeb.68.1426812665807;
 Thu, 19 Mar 2015 17:51:05 -0700 (PDT)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Received: by 10.202.58.2 with HTTP; Thu, 19 Mar 2015 17:50:25 -0700 (PDT)
In-Reply-To: <CAGa2bXb2qm3Y0S_dVDe+Orh6kbuuQOOgLNc_VwycZCCiSxPZ2w@mail.gmail.com>
References: <CAGa2bXb2qm3Y0S_dVDe+Orh6kbuuQOOgLNc_VwycZCCiSxPZ2w@mail.gmail.com>
Date: Fri, 20 Mar 2015 09:50:25 +0900
X-Google-Sender-Auth: LGRbK8GcBYpd4ILyk21cqKWcGLI
Message-ID: <CAGa2bXa1Z0_9eMhYY7nmCWM1+DDAMOtQZrtPpsK3vVz_wuJ9Yw@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0116126e1b496f0511adb6f8
Subject: Re: Bug #69127 session_regenerate_id(true) randomly generates a
 warning and loses session data
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0116126e1b496f0511adb6f8
Content-Type: text/plain; charset=UTF-8

Hi all,

On Sun, Mar 1, 2015 at 1:53 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:

> There are too many things that I would like to improve ;)
>
> https://bugs.php.net/bug.php?id=69127
>
> This bug is known fatal bug for session module. I proposed "lazy_destroy"
> to fix
> this before, but it declined.
>
> I think the name was wrong. With the proposal, session module destories
> session data with lazy manner, but it's actually precise manner. i.e.
> Session
> module and browser is _not_ synced, so destroy must be done async manner
> (~= lazy manner. For example, delete session data 60 seconds later).
>
> The reason why session_regenerate_id(true) fails is it deletes session
> data
> immediately even if session and browser is not in sync. Session and
> browser
> cannot sync because there is no means in HTTP/Cookie.
>
> Is there any other better idea for this?
>

I've updated old RFC for this bug fix.

https://wiki.php.net/rfc/session_regenerate_id

I would like to start discussion shortly. If anyone would like to comment
now,
I appreciate it.

Thank you.

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0116126e1b496f0511adb6f8--