'WSGIRequest' object has no attribute 'session' while upgrading from django 1.3 to 1.9

Question

Similar to this question 'WSGIRequest' object has no attribute 'session'

But my MIDDLEWARE classes are in the correct order.

INSTALLED_APPS = [
    'django.contrib.sessions',
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.messages',
    'django.contrib.staticfiles',
    'membership',
    'treebeard',
    'haystack',
    'reversion',
]

MIDDLEWARE = [
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.security.SecurityMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

I am redirecting to login

url(r'^$',  RedirectView.as_view(url='login/')),
url(r'^login/$', 'membership.views.loginView', name='login'),

and then

def loginView(request):
    a = request.session

Throws the error

score 26 · Accepted Answer · answered Sep 13 '16 at 23:18

MIDDLEWARE is a new setting in 1.10 that will replace the old MIDDLEWARE_CLASSES.

Since you're currently on 1.9, Django doesn't recognize the MIDDLEWARE setting. You should use the MIDDLEWARE_CLASSES setting instead:

MIDDLEWARE_CLASSES = [
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.security.SecurityMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

Django 2.0 uses `MIDDLEWARE` now instead of `MIDDLEWARE_CLASSES`, as pointed out by @Slipstream and [in this thread](https://stackoverflow.com/a/47650447/1218179) — mateuszb, Mar 25 '18 at 23:01

score 18 · Answer 2 · edited Jun 20 '20 at 09:12

Django 2.0

You can try this in your settings.py, MIDDLEWARE_CLASSES = [....]:

Change MIDDLEWARE_CLASSES=[...] to MIDDLEWARE=[...]
Remove SessionAuthenticationMiddleware from the MIDDLEWARE=[...] list.

The MIDDLEWARE_CLASSES setting is deprecated in Django 1.10, and removed in Django 2.0.

The SessionAuthenticationMiddleware class is removed. It provided no functionality since session authentication is unconditionally enabled in Django 1.10.

score 5 · Answer 3 · answered Feb 03 '19 at 18:24

5

This error can also be thrown when you have a typo. i.e.

request.sesion ...

instead of

request.session ...

answered Feb 03 '19 at 18:24

Michel K

641
1
6
18

4

I was laughing when I read your possible solution! Then I checked and I had done the exact same typo. Now I am laughing in tears – Hashir Apr 27 '21 at 23:34
And it's request.session, not request.sessions..... :( – Rishi Latchmepersad Mar 11 '22 at 19:51
haha, same here, I did with 3s – heschmat Nov 21 '22 at 14:13

Thomas John · Answer 4 · 2018-01-30T04:50:05.523

2

Check the order of the middleware, if you are trying to access it on some middlewares which are listed above the session middleware, you will get this error.

edited Jan 30 '18 at 04:50

answered Jan 16 '18 at 10:18

Thomas John

2,138
2
22
38

'WSGIRequest' object has no attribute 'session' while upgrading from django 1.3 to 1.9

4 Answers4

Linked