-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Security] login_check route throws exception on php 5.4.4: Parent session handler is not open #13269
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
Comments
Well, you are installing a development snapshot, those are known not to be stable. You could try to find the commit causing this by using |
I know and this is not a complaint, just a report. Should I really wait until a final 2.6.2 release before reporting problems? And to be fair: it's a development snapshot of a bugfix release. :-) |
Reporting problems can always be done, IMO rather sooner than later. |
Since that commit went into the LTS branch, I've just checked the other branches. I could reproduce this problem with latest 2.3 and 2.5 as well. |
I found some related resources. It is probably this PHP bug https://bugs.php.net/bug.php?id=63379 for PHP <= 5.4.11. There was an issue #5868 describing the same problem, but related to the logout handler, which results in adding a recommendation to SymfonyRequirements.php (sensiolabs/SensioDistributionBundle@2a518e7). I see three options:
|
As the "fix" went into 2.3, I would vote for reverting the change for now and open a new ticket explaining everything mentioned here. |
Thanks for the quick answer, @xelaris. I digged into that issue and came to the same conclusion. I'm in favor for option two, since your patch works well on reasonably new php versions. Adding a new strategy just because of old quirky php versions is overkill, imho. I'd like to keep that complexity out of the framework configuration. |
As an alternative, I've created PR #13286 with the change we've discussed. |
…. (derrabus) This PR was squashed before being merged into the 2.3 branch (closes #13286). Discussion ---------- [Security] Don't destroy the session on buggy php releases. | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #13269, #13283 | License | MIT | Doc PR | none See #13269 for the discussion. This workaround avoids destroying the old session after login on the migrate strategy when running under a php version that we know to be broken. Corresponding php bug: https://bugs.php.net/bug.php?id=63379 Commits ------- 5d0b527 [Security] Don't destroy the session on buggy php releases.
I tried to upgrade my client's Symfony application from 2.5.8 to the lastest 2.6-dev snapshot (12d8261). Unfortunately, the upgrade broke their login process completely, which worked fine with 2.6.1 and below.
I could reproduce the problem by creating a new Symfony Standard application and implementing a login form as described in the cookbook. If I enter correct credentials in the form here, I get the following exception on the login_check route.
This problem only appears on our old virtual machine running php 5.4.4. On my dev machine running Ubuntu 14.10 with the bundled php 5.5.12, everything works as expected. So, this issue is probably related to that old php version. Maybe, we're facing a similar issue here as in #5868 (just guessing)?
My client is aware, that this php version is fairly old, but the application has several hundred installations and most of them under that old php version, so the migration to a more recent php release will take some time. Untill then, I would need a fix or a workaround.
The text was updated successfully, but these errors were encountered: