Cookie names were hardcoded to pretty generic names `'session'` and `'session_data'`, respectively. They might potentially clash with other similar named cookies, especially when developing locally. Added oak_ prefix to the default ones. Can theoretically be considered breaking change, as if user has active session, and the application below restarts with middleware upgraded to this change, middleware would consider user not having a session and thus requiring a new session init. With semi-short sessions it doesn't matter, but ofc there might be use case where it is expected for the session cookie to be there for very long time. Any thoughts come up about this cookie renaming?
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by Snurppa and has received 2 comments.
Add a comment
Comment form would go here