เฟรมเวิร์กเซสชัน

HTTP forgets you between requests. The session framework lets Django remember each visitor across page loads, so a login or a cart can survive. 🍪

A session is a small bag of data tied to one visitor. Django keeps it on the server and gives the browser only a key to find it again.

Django sets a cookie named sessionid in the browser. That cookie holds just the session key, never your private data, which stays safe on the server.

The SessionMiddleware ships enabled in every new project, so sessions work out of the box without any extra setup from you.

The django.contrib.sessions app lives in INSTALLED_APPS and creates a table to hold session data after you run migrate.

By default Django stores sessions in the database. Each row holds the key, the encoded data, and an expiry date for that visitor.

You pick storage with SESSION_ENGINE. Cache or cached_db backends keep sessions in memory for far faster reads on busy sites.

In any view, the session hangs off the request as request.session. It behaves like a normal Python dictionary you can read and write.

Sessions do not last forever. SESSION_COOKIE_AGE sets the lifetime in seconds, defaulting to two weeks before a visitor is forgotten.

Expired rows linger in the database. Run clearsessions on a schedule to delete stale data and keep the table tidy.

Sessions track both anonymous and logged-in visitors. That is how a guest can fill a cart before they ever create an account.

Let us check where session data actually lives.

You met the session framework: it remembers visitors across requests, stores data server-side, and works automatically through SessionMiddleware. Next you will read and write it. ✅