File tree Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Original file line number Diff line number Diff line change @@ -68,7 +68,9 @@ Configuration
6868 * `gc_divisor `_
6969 * `gc_probability `_
7070 * `gc_maxlifetime `_
71+ * `use_strict_mode `_
7172 * `save_path `_
73+ * `metadata_update_threshold `_
7274* `assets `_
7375 * `base_path `_
7476 * `base_urls `_
@@ -809,6 +811,17 @@ This determines the number of seconds after which data will be seen as "garbage"
809811and potentially cleaned up. Garbage collection may occur during session
810812start and depends on `gc_divisor `_ and `gc_probability `_.
811813
814+ use_strict_mode
815+ ...............
816+
817+ **type **: ``boolean `` **default **: ``false ``
818+
819+ This specifies whether the session module will use the strict session id mode.
820+ If this mode is enabled, the module does not accept uninitialized session IDs.
821+ If an uninitialized session ID is sent from browser, a new session ID is sent
822+ to browser. Applications are protected from session fixation via session
823+ adoption with strict mode.
824+
812825save_path
813826.........
814827
@@ -855,6 +868,19 @@ setting the value to ``null``:
855868 ),
856869 ));
857870
871+ metadata_update_threshold
872+ .........................
873+
874+ **type **: ``integer `` **default **: ``0 ``
875+
876+ This is how many seconds to wait between two session metadata updates. It will
877+ also prevent the session handler to write if the session has not changed.
878+
879+ .. seealso ::
880+
881+ You can see an example of the usage of this in
882+ :doc: `/session/limit_metadata_writes `.
883+
858884assets
859885~~~~~~
860886
You can’t perform that action at this time.
0 commit comments