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/4.0/ref/settings/#session-cookie-name)?
> I wonder if using a Django project code name as part of session cookie for new projects would have a potential to be considered as an accepted feature. has not been considered (as far as I know) and is something I'd be strongly against. Cheers, Florian On Monday, June 6, 2022 at 11:51:24 PM UTC+2 macie...@gmail.com wrote: > 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. Majority of > users use only one of services in day-to-day work, so it's not impacting a > big number of people. > > I personally would be +1 for exposing a method to easily and without > copying much code one was able to change it. > > I wonder if using a Django project code name as part of session cookie for > new projects would have a potential to be considered as an accepted feature. > > Kind regards, > Maciej > > pon., 6 cze 2022 o 22:19 Dan Strokirk <d...@kundo.se> napisał(a): > >> 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 since I haven't found a similar request earlier on this mailing list >> or the issue tracker, it seems that it might be really niche, as you say! >> >> Best regards, >> Dan >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/01a91019-8d54-4322-a295-dbfdc12dfab9n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/01a91019-8d54-4322-a295-dbfdc12dfab9n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/08a438ff-9d7a-47e0-abe2-d68a7dd20935n%40googlegroups.com.
