You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The custom error handlers throw an exception when there is no valid session. This results in a fatal error, early enough to cause PHP to display a blank 500 error to end users.
To Reproduce
Throw any unhandled exception before the creation of a valid session.
For example, the exception thrown by unserialize() when trying to read an existing 1.19.x session will reliably trigger this.
Expected behavior
A helpful error message to be displayed to the user :-)
This probably requires a transient session to be created by the handler if there isn't a valid one.
Screenshots or logs
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Typed property SimpleSAML\\Session::$trackid must not be accessed before initialization in /home/safire/simplesamlphp-2.0.3/src/SimpleSAML/Session.php:552
Stack trace:
#0 /home/safire/simplesamlphp-2.0.3/src/SimpleSAML/Session.php(399): SimpleSAML\\Session->getTrackID()
#1 /home/safire/simplesamlphp-2.0.3/src/SimpleSAML/Session.php(281): SimpleSAML\\Session::load()
#2 /home/safire/simplesamlphp-2.0.3/src/SimpleSAML/Error/Error.php(191): SimpleSAML\\Session::getSessionFromRequest()
#3 /home/safire/simplesamlphp-2.0.3/src/SimpleSAML/Error/Error.php(229): SimpleSAML\\Error\\Error->saveError()
#4 /home/safire/simplesamlphp-2.0.3/public/_include.php(32): SimpleSAML\\Error\\Error->show()
#5 [internal function]: SimpleSAML_exception_handler()
#6 {main}
thrown in /home/safire/simplesamlphp-2.0.3/src/SimpleSAML/Session.php on line 552`
The text was updated successfully, but these errors were encountered:
Describe the bug
The custom error handlers throw an exception when there is no valid session. This results in a fatal error, early enough to cause PHP to display a blank 500 error to end users.
To Reproduce
Throw any unhandled exception before the creation of a valid session.
For example, the exception thrown by unserialize() when trying to read an existing 1.19.x session will reliably trigger this.
Expected behavior
A helpful error message to be displayed to the user :-)
This probably requires a transient session to be created by the handler if there isn't a valid one.
Screenshots or logs
The text was updated successfully, but these errors were encountered: