fix: set DestroySession MaxAge to -1 instead of -1*time.Second (closes #39) #50
In neuem Issue referenzieren
Einen Benutzer sperren
Branch ":fix/destroy-session-maxage" löschen
Das Löschen eines Branches ist permanent. Obwohl der Branch für eine kurze Zeit weiter existieren könnte, kann diese Aktion in den meisten Fällen NICHT rückgängig gemacht werden. Fortfahren?
Summary
Fixes the
DestroySessionmethod which was settingMaxAge = -1 * int(time.Second)(resulting in-1000000000) instead of simply-1.The gorilla/sessions
MaxAgefield expects a value in seconds. The previous code multiplied bytime.Second(nanoseconds), which worked by accident since any negative value deletes the cookie, but was semantically incorrect.Changes
internal/service/auth/auth.go: ChangedMaxAge = -1 * int(time.Second)toMaxAge = -1; removed unusedtimeimportinternal/service/auth/auth_test.go: AddedTestDestroySessionMaxAgetest(closes #39)
Test Results ✅
All tests pass:
All other packages also pass (database, docker, handlers, middleware, models, app, webhook, ssh).
Lint Results ✅
No new lint issues. One pre-existing issue in
internal/handlers/tail_validation_test.go(wrong package name) — not related to this change.