Pārlūkot izejas kodu

Allow custom session handlers to work correctly (and be defined at the application level with SquirrelMail) -- TODO: Cannot forget to add info about this to the docs!

pdontthink 17 gadi atpakaļ
vecāks
revīzija
990a2741a3
2 mainītis faili ar 47 papildinājumiem un 0 dzēšanām
  1. 2 0
      ChangeLog
  2. 45 0
      include/init.php

+ 2 - 0
ChangeLog

@@ -227,6 +227,8 @@ Version 1.5.2 - SVN
     etc. (#1818398).
     etc. (#1818398).
   - PAGE_NAME might not be defined in all plugins, which might cause a
   - PAGE_NAME might not be defined in all plugins, which might cause a
     "not defined" error on session timeouts.
     "not defined" error on session timeouts.
+  - Allow custom session handlers to work correctly (and be defined at the
+    application level with SquirrelMail).
 
 
 Version 1.5.1 (branched on 2006-02-12)
 Version 1.5.1 (branched on 2006-02-12)
 --------------------------------------
 --------------------------------------

+ 45 - 0
include/init.php

@@ -251,6 +251,51 @@ if (PAGE_NAME == 'login') {
     if (!empty($_SESSION))
     if (!empty($_SESSION))
         $_SESSION = array();
         $_SESSION = array();
 
 
+    /**
+     * Allow administrators to define custom session handlers
+     * for SquirrelMail without needing to change anything in
+     * php.ini (application-level).
+     *
+     * In config_local.php, admin needs to put:
+     *
+     *     $custom_session_handlers = array(
+     *         'my_open_handler',
+     *         'my_close_handler',
+     *         'my_read_handler',
+     *         'my_write_handler',
+     *         'my_destroy_handler',
+     *         'my_gc_handler',
+     *     );
+     *     session_module_name('user');
+     *     session_set_save_handler(
+     *         $custom_session_handlers[0],
+     *         $custom_session_handlers[1],
+     *         $custom_session_handlers[2],
+     *         $custom_session_handlers[3],
+     *         $custom_session_handlers[4],
+     *         $custom_session_handlers[5]
+     *     );
+     *
+     * We need to replicate that code once here because PHP has
+     * long had a bug that resets the session handler mechanism
+     * when the session data is also destroyed.  Because of this
+     * bug, even administrators who define custom session handlers
+     * via a PHP pre-load defined in php.ini (auto_prepend_file)
+     * will still need to define the $custom_session_handlers array
+     * in config_local.php.
+     */
+    global $custom_session_handlers;
+    if (!empty($custom_session_handlers)) {
+        $open    = $custom_session_handlers[0];
+        $close   = $custom_session_handlers[1];
+        $read    = $custom_session_handlers[2];
+        $write   = $custom_session_handlers[3];
+        $destroy = $custom_session_handlers[4];
+        $gc      = $custom_session_handlers[5];
+        session_module_name('user');
+        session_set_save_handler($open, $close, $read, $write, $destroy, $gc);
+    }
+
     sqsession_is_active();
     sqsession_is_active();
     session_regenerate_id();
     session_regenerate_id();