Ajoutez des fichiers projet.
This commit is contained in:
35
venv/Lib/site-packages/django/contrib/sessions/models.py
Normal file
35
venv/Lib/site-packages/django/contrib/sessions/models.py
Normal file
@@ -0,0 +1,35 @@
|
||||
from django.contrib.sessions.base_session import (
|
||||
AbstractBaseSession, BaseSessionManager,
|
||||
)
|
||||
|
||||
|
||||
class SessionManager(BaseSessionManager):
|
||||
use_in_migrations = True
|
||||
|
||||
|
||||
class Session(AbstractBaseSession):
|
||||
"""
|
||||
Django provides full support for anonymous sessions. The session
|
||||
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).
|
||||
"""
|
||||
objects = SessionManager()
|
||||
|
||||
@classmethod
|
||||
def get_session_store_class(cls):
|
||||
from django.contrib.sessions.backends.db import SessionStore
|
||||
return SessionStore
|
||||
|
||||
class Meta(AbstractBaseSession.Meta):
|
||||
db_table = 'django_session'
|
Reference in New Issue
Block a user