Class Session

django.contrib.sessions.models.Session

Django provides full support for anonymous sessions. The session

Declaration

Documentation

framework lets you store and retrieve arbitrary data on a
per-site-visitor basis. It stores data on the server side and
abstracts the sending and receiving of cookies. Cookies contain a
session ID -- not the data itself.

The Django sessions framework is entirely cookie-based. It does
not fall back to putting session IDs in URLs. This is an intentional
design decision. Not only does that behavior make URLs ugly, it makes
your site vulnerable to session-ID theft via the "Referer" header.

For complete documentation on using Sessions in your code, consult
the sessions documentation that is shipped with Django (also available
on the Django Web site).

Class methods

▶ def get_session_store_class(cls) override @classmethod
@classmethod
def get_session_store_class(cls)
source link
This method overrides django.contrib.sessions.base_session.AbstractBaseSession.get_session_store_class.

Inherited methods

Methods inherited from django.contrib.sessions.base_session.AbstractBaseSession:
__str__, get_decoded
Methods inherited from django.db.models.base.Model:
__eq__, __getstate__, __hash__, __init__, __reduce__, __repr__, __setstate__, check, clean, clean_fields, date_error_message, delete, from_db, full_clean, get_deferred_fields, prepare_database_save, refresh_from_db, save, save_base, serializable_value, unique_error_message, validate_unique