Ah, thank you for explaining. I missed the point and the existing setting,
sorry.
Cheers,
Maciej
wt., 7 cze 2022 o 11:26 Florian Apolloner
napisał(a):
> Hi Maciej,
>
> You can already customize the cookie name via a setting. What this request
> is asking is customization based on the request ob
Hi Maciej,
You can already customize the cookie name via a setting. What this request
is asking is customization based on the request object which is not that
common. Did you check that you configured your applications correctly to
use different cookie names
(https://docs.djangoproject.com/en/
Hi Dan and Carlton,
In my current company I am impacted by conflicting session cookie name. We
have several internal tools built on Django, available in the internal
network under the same top-level domain. The scope of session cookies
apparently was set on more than one service to a wildcard. Maj
Hi Carlton, thanks for the response.
An external package might be useful, although the code majority of the code
would be the copied SessionMiddleware code and the tiny changes to allow a
dynamic cookie name, so my thoughts is that this might be "too small" for a
published pypi package?
But si
Hey Dan.
Thanks for following up here.
Just to recap, my reasoning on the ticket was that it's quite a niche
use-case. For me, just use the custom SessionMiddleware, or put that in a
third-party package for multi-tenancy folks to maintain together. (Or so
would be my opening thought... -- interes
Hi,
Currently it's only possible to use a single session cookie, but it can be
useful in a multi-tenant application to use multiple session cookies. To
solve this we currently use our own, slightly modified SessionMiddleware
class that we keep in sync with the official implementation and re-app
