php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #37615 session_is_persistent
Submitted: 2006-05-27 14:35 UTC Modified: 2006-06-01 14:11 UTC
From: elias at adaptiveinstance dot com Assigned:
Status: Wont fix Package: Session related
PHP Version: 5.1.4 OS: all
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: elias at adaptiveinstance dot com
New email:
PHP Version: OS:

 

 [2006-05-27 14:35 UTC] elias at adaptiveinstance dot com 
Description:
------------
There is no reliable way to determine if the session has already been closed with session_write_close() or not. a function like session_is_persistent() would be needful to validate that changes to $_SESSION will be written.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2006-05-27 14:45 UTC] tony2001@php.net 
There is also no way to determine if any other function has been called, but that doesn't mean we're going to add new functions for that.
 [2006-05-27 15:23 UTC] elias at adaptiveinstance dot com 
thats not what's on my mind at all. i think adding an internal flag that tracks if session_write_close() was called isn't that hard.
 [2006-06-01 14:11 UTC] elias at adaptiveinstance dot com 
its ok if there is in general no interest in this feature, but dismissing bugreports with half-assed answers isn't. so  give me a good reason why this shouldn't be possible or tell me there is no need/interest for this.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Fri May 09 15:01:27 2025 UTC