-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[HttpFoundation] Fix regression of delegation of Session::save() to Storage::Save() #31215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -219,6 +219,12 @@ public function regenerate($destroy = false, $lifetime = null) | |
*/ | ||
public function save() | ||
{ | ||
// In PHP <7.2 session_write_close() does not error if the session is | ||
// not started. | ||
if (!$this->started) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I thought about this approach as well. I hesitated to go this way because of the phpdoc on the interface: Not sure if this would not also be a BC break as someone is relying on this? 😕 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually it seems this see #6362 Edit: but anyway this means if a storage is used that throws an exception on save without being started then this would fail now if the kernel is reset on a non-started (but instantiated) session. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we catch that exception in Session::save() and convert it to a warning or deprecation error saying that the storage needs to handle an attempt to save a reset session on its own? The behavior that you describe is what existed prior to this BC break in 3.4.24 for custom storage, prior to that they would have had to handle a reset session on their own anyway. |
||
return; | ||
} | ||
|
||
$session = $_SESSION; | ||
|
||
foreach ($this->bags as $bag) { | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -261,13 +261,4 @@ public function testIsEmpty() | |
$this->assertTrue($this->session->isEmpty()); | ||
} | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. extra line should be removed |
||
public function testSaveIfNotStarted() | ||
{ | ||
$storage = $this->getMockBuilder('Symfony\Component\HttpFoundation\Session\Storage\SessionStorageInterface')->getMock(); | ||
$session = new Session($storage); | ||
|
||
$storage->expects($this->once())->method('isStarted')->willReturn(false); | ||
$storage->expects($this->never())->method('save'); | ||
$session->save(); | ||
} | ||
} |
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe this should be written as
In PHP >=7.2 session_write_close() errors if the session is not started?
(single line please)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to say that this is following the logic of session_write_close in PHP <7.2 - in PHP >=7.2 it returns FALSE.
However I've just read the docs on the interface which say
So now I'm not sure what's the right thing to do. What's clear is that is not what \Symfony\Component\HttpFoundation\Session\Storage\NativeSessionStorage::save() does in 3.4 HEAD.