You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Neither this call nor simple_module_hosting/session.py passes https_only, so the session cookie has no Secure attribute. In production it can travel over plain HTTP, for example on the first request before HSTS is cached, or behind a misconfigured proxy.
This matters more here than usual because CSRF defence relies on SameSite=Lax alone. The opt-in token (simple_module_hosting.csrf) is used in only two places.
Fix
https_only=not settings.is_development, or a HostSettings.session_cookie_secure field that defaults on outside development.
Add a test asserting Secure appears in Set-Cookie when not in development.
Mention it in the deployment docs, since installs that serve plain HTTP on purpose behind a TLS terminator need SM_TRUSTED_PROXY set.
Activity
fix: tenancy, boot-config, audit and session-cookie bug batch (#494 #495