-
Notifications
You must be signed in to change notification settings - Fork 430
The django_util session data does not work with Django 1.10 #594
Comments
Acknowledged. |
@huwshimi , I'm having trouble reproducing this. I just ran it with Python 3.5.2 and Django 1.10.0 and it works fine for me. The docs say that by default the serializer uses JSON. So I'm wondering why I am not reproducing this issue. I can keep looking into it, but any hints as to something I might be doing?
|
I am wondering if it's something about that specific Flow... |
@waprin Thanks for taking a look. It could well be something to do with my project setup (this is an old project that has been upgraded to Django 1.10). It could even be the data I'm passing in. If I figure out what it is, I'll add the details here. |
Just out of curiosity what database are you using? |
Never mind, able to reproduce it, was using localhost but actual server repros it, will work on it now. |
@waprin Thanks heaps, I'll give it a go! |
The session serialiser with Django 1.10 does not support picked data, like that attached to the session here: https://github.com/google/oauth2client/blob/master/oauth2client/contrib/django_util/views.py#L74
This is the error received:
Switching the session serialiser to
PickleSerializer
resolves the issue, but is not recommended due to security concerns.SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer'
More info can be found at: https://docs.djangoproject.com/en/1.10/topics/http/sessions/#session-serialization
The text was updated successfully, but these errors were encountered: