An attacker can send the CSRF file to the victim or host it on a website. Setting the session expiry in middleware has side effects of doing a session change in every request, which is not desired. It also forces session creation when there is no session needed. The logic is now reverse - the session's default to shorter lifespan, which is used for anonymous sessions, and authenticated ones have separate settings to set their validity which is set on login. The session has to exist at this point and we are changing it just once per session lifetime. Fixed in Weblate 4.3