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
If for whatever reason a session has a cookie with an expires in the past then a call to set results in a negative TTL that's calculated which in turn leads to Redis throwing an error ERR invalid expire time in set.
Suggestion: the set method could check for the TTL it calculates and if it results in a negative TTL it could immediately delete / destroy the key.
The text was updated successfully, but these errors were encountered:
baumgarb
pushed a commit
to baumgarb/connect-redis
that referenced
this issue
Apr 20, 2021
If the set method is invoked with a session object which has a cookie
that expires in the past then the key is deleted / destroyed. Otherwise,
a negative TTL is calculated and that leads to Redis throwing an error
'ERR invalid expire time in set'.
baumgarb
pushed a commit
to baumgarb/connect-redis
that referenced
this issue
Apr 20, 2021
If the set method is invoked with a session object which has a cookie
that expires in the past then the key is deleted / destroyed. Otherwise,
a negative TTL is calculated and that leads to Redis throwing an error
'ERR invalid expire time in set'.
If for whatever reason a session has a cookie with an
expires
in the past then a call toset
results in a negative TTL that's calculated which in turn leads to Redis throwing an errorERR invalid expire time in set
.Suggestion: the
set
method could check for the TTL it calculates and if it results in a negative TTL it could immediately delete / destroy the key.The text was updated successfully, but these errors were encountered: