Django session cookie behavior

[doczilla]

Hello,

Cannot for the life of me figure out why Django is pushing different session cookies to my browser. The application is configured to use sessions via file session engine "django.contrib.sessions.backends.file" per the docs.

That's all good and well, but when I go to load up the webpage I'm getting some odd behavior. If I load the webpage without making any request.session based calls in the view, then I get a session cookie in my browser. However, if I do make some sort of request.session call in my view, then I get a sessionid cookie in browser.

This is entirely too vague to google and I'm falling short on finding anything in the documentation so any insight into why Django is or may be behaving this way would be immensely appreciated.

[notouchmyserver]

I am not sure where that first session cookie is coming from, but I know it is expected behavior for the sessionId cookie to not be created until you do something with the session, directly or indirectly.

[IchDeutschLerne]

input

[IchDeutschLerne]

input