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
Do you want to request a feature or report a bug?
bug
What is the current behavior?
The value of maxAge for the cookie of the session-cookie is set as is (which will be treated as seconds). But the code treats this value as milli-seconds when cleaning the SessionCookie cache.
If the current behavior is a bug, please provide the steps to reproduce.
Set maxAge to a number of seconds. You will see the browser keep sending the cookie for that amount of time, But the cookie will be lost and a new one created after that amount of milliseconds.
What is the expected behavior?
The middletier should keep the SessionCookie for maxAge*1000
Please mention your java and java-express version.
version 0.2.1
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: