Tweet
User session hash on /login.php redirect
Hi all,
I need some help with php/vbulletin templating system. I have setup nginx as reverse proxy which caches every single page on the site for 1 minute. This works great for visitors(not logged in users) and also logged in users. For logged in users, i cache every single page by appending user's bbsessionhash cookie value. This is working great and the site is super fast, my only problem is with the login process.
Since the user can login from the nav_bar by filling out the form on any page on the site, the login redirect is landing the user on the same cached page. Since the redirect is setting the bbsessionhash cookie value for the first time, the user sees the "Login successfull" redirect screen but than lands on the previous cached copy of that page in the browser.
So what i need is to update the login template, to append a unique identifier to the redirect url: something like ?loginhash=<some_unique_session_id> so that when the user logs in i can bust the browser cache.
The unique identifier can be anything, current time in nanoseconds, php session id, etc. It just has to be unique for that specific user. I don't know much about vbulletin's templating system, that is why i need help.
Once i solve this last remaining problem, i will write a tutorial for it.
Thanks in advance.
P.S I am running an older version of vbulletin: 3.6.8
I need some help with php/vbulletin templating system. I have setup nginx as reverse proxy which caches every single page on the site for 1 minute. This works great for visitors(not logged in users) and also logged in users. For logged in users, i cache every single page by appending user's bbsessionhash cookie value. This is working great and the site is super fast, my only problem is with the login process.
Since the user can login from the nav_bar by filling out the form on any page on the site, the login redirect is landing the user on the same cached page. Since the redirect is setting the bbsessionhash cookie value for the first time, the user sees the "Login successfull" redirect screen but than lands on the previous cached copy of that page in the browser.
So what i need is to update the login template, to append a unique identifier to the redirect url: something like ?loginhash=<some_unique_session_id> so that when the user logs in i can bust the browser cache.
The unique identifier can be anything, current time in nanoseconds, php session id, etc. It just has to be unique for that specific user. I don't know much about vbulletin's templating system, that is why i need help.
Once i solve this last remaining problem, i will write a tutorial for it.
Thanks in advance.
P.S I am running an older version of vbulletin: 3.6.8
Comment