Fixed Bug #71038 session_start() returns TRUE on failure #1721
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Although I prefer maintaining FAILURE/SUCCESS status by return values, it's possible to use PS(session_status) to return proper status from session_start().
This patch fixes
https://bugs.php.net/bug.php?id=71038
The destructive part is
This breaks save handlers returns broken return value (false/FAILURE) for successful read.
Note: Reading non-existing session data (new session ID data) must be SUCCESS because there is no error at all and must return true/SUCCESS.
This change is BC for PHP 5.6, but not for PHP7 since it does not allow broken return value from PS(mod)->s_read.
For user save handlers using file_get_contents(), the only required change is cast to string like test files.
Question is if we should fix this bug in PHP 5.6 or not.
Other possible option is ignore s_read() error at all in PHP 5.6 to be compatible.
If nobody cares, I would like to choose 2nd (ignore read errors) option for PHP 5.6.
Any comments?
Note: One fpm test fails, but it should be irrelevant.