Home > Back-end >  Using redis store session encounter problems
Using redis store session encounter problems

Time:09-28

Our current website design with redis store after each user login sessionId and session (respectively as the key and the value), now the default expiry time (without receiving the instructions to the user from after timing) is 30 minutes, 30 minutes after the session is deleted, the user will also automatically logged out,
I hope to set the time for 60 minutes, now I have modified the properties file for this

But it does not work, I have modified the user center module (ucenter) code, this part is to write the session after the user login redis,


But now I find that when I enter the site of a page, check it on the redis can session expiration time is 3600, but switch to other web pages, query again the same session (TTL) key queries, expiration time is 1800, has now become a feeling like to set the expiration time, only this is a web page 3600, the web page and other difference is that he is using the other functions in the ucenter, so I wonder could it be so,

Want to know what method to solve this problem, I can't find in other web page code about redis this part of the set, thank you very much!!!!!!!!!!

CodePudding user response:

Look from code, your redis login is ucenter responsible, the session timeout time is set at storeSession,
Switch to some other web page, the background is how to control the page jump? You cannot look at other business logic code of the page, to view the entire control part receives the request, such as the filter interceptor code, etc., to see if the session did what other processing, such as a permission to handle authentication access through again after reset the session, such as

CodePudding user response:

reference 1st floor qybao response:
code from your redis login ucenter is responsible, the session timeout time is set at storeSession,
Switch to some other web page, the background is how to control the page jump? You cannot look at other business logic code of the page, to view the entire control part receives the request, such as the filter interceptor code, etc., to see if the session did what other processing, such as a permission to handle authentication access through again after reset the session, such as


Is. An XML file to see this page, such as the configuration of the jump?
  • Related