Re: Re: Fixing insane session_start() behaviors
| From: | Yasuo Ohgaki | Date: | Wed, 19 Oct 2016 12:17:01 +0000 |
| Subject: | Re: Re: Fixing insane session_start() behaviors | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-96476@lists.php.net to get a copy of this message | ||
Hi Stas,
On Wed, Oct 19, 2016 at 8:57 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Only valid use case is
>
> <?php
> ob_start();
> session_start();
> session_set_cache_limiter('public'); // <== Call this between
> session_start() and session_regenerate_id()
> session_regenerate_id();
> ?>
>
> Other than this, all calls after session_start() is invalid. Valid use
> case is very limited and unlikely. If users have to change cache
> limiter, they can session_commit(), then session_start(). So I would
> like to keep as it is now.
I thought php_session_reset_id() sends all headers, but it sends only
session ID cookie header. So current code is good. Sorry for
confusion.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net