would be set to a relatively large number of days, weeks or months.It is not uncommon to set cookies for a year or more depending on the application.

They must be configured by Note Native save handlers provide a quick solution to session storage, however, in complex systems where you need more control, custom save handlers may provide more freedom and flexibility.

Symfony provides several implementations which you may further customize as required.

Custom handlers are those which completely replace PHP's built-in session save handlers by providing six callback functions which PHP calls internally at various points in the session workflow.

The Symfony Http Foundation component provides some by default and these can easily serve as examples if you wish to write your own.

This is calculated by adding the PHP runtime configuration value in Note PHP will only issue a cookie once.

The client is expected to store that cookie for the entire lifetime.

A new cookie will only be issued when the session is destroyed, the browser cookie is deleted, or the session ID is regenerated using the There are often circumstances where you may want to protect, or minimize unauthorized use of a session when a user steps away from their terminal while logged in by destroying the session after a certain period of idle time.

This section deals with how to configure session management and fine tune it to your specific needs.

This documentation covers save handlers, which store and retrieve session data, and configuring session behavior.

So-called native handlers, are save handlers which are either compiled into PHP or provided by PHP extensions, such as PHP-Sqlite, PHP-Memcached and so on.

All native save handlers are internal to PHP and as such, have no public facing API.