Unable to modify Session with signed_cookies backend

[Krishna Chaitanya]

Hi, 

When I try to modify a session when using signed_cookies backend it creates a new session which voids

the purpose as I am using session_key as a shared data structures across views/functions.

Is this expected or a bug? I am using 1.11 (default on ubuntu 18.04, can't update as pip isn't allowed), but even

looking at the latest source https://github.com/django/django/blob/master/django/contrib/sessions/backends/signed_cookies.py#L41

the behavior isn't changed.

The same logic works fine with db/file backends but can't use that due to low storage issues.

Any help is appreciated?

Thanks

[Ogunsanya Opeyemi]

Hi,

Serach for pip install url on ubuntu then you for you to get pip installed.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e399f194-2fd7-4fae-a002-7599badce3b3o%40googlegroups.com.

--

OGUNSANYA OPEYEMI

[Krishna Chaitanya]

Hi,

Thanks. I know how to isntallle using pip but pip isn't installed in our devices, and moreover there is no difference in the code with layers version.

On Sat, 4 Jul, 2020, 8:04 am Ogunsanya Opeyemi, <ogunsany...@gmail.com> wrote:

Hi,

Serach for pip install url on ubuntu then you for you to get pip installed.
On Friday, July 3, 2020, Krishna Chaitanya <chaitan...@gmail.com> wrote:

Hi, 

When I try to modify a session when using signed_cookies backend it creates a new session which voids

the purpose as I am using session_key as a shared data structures across views/functions.

Is this expected or a bug? I am using 1.11 (default on ubuntu 18.04, can't update as pip isn't allowed), but even

looking at the latest source https://github.com/django/django/blob/master/django/contrib/sessions/backends/signed_cookies.py#L41

the behavior isn't changed.

The same logic works fine with db/file backends but can't use that due to low storage issues.

Any help is appreciated?

Thanks

--
You received this message because you are subscribed to the Google Groups "Django users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/e399f194-2fd7-4fae-a002-7599badce3b3o%40googlegroups.com.

--

OGUNSANYA OPEYEMI

--
You received this message because you are subscribed to the Google Groups "Django users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABJxPrGaq7b53Ev4HkuZ93XYrwJ5njOS1CCsZ9Gxn%3D-hDKLU0Q%40mail.gmail.com.