09-14-2016, 10:29 AM
I had to go back to my original solution, putting Brian's solution in place means that when the session should be expired you get a nasty double load page, since headers had already been sent to page (not sure which since it is really fast) but there was this white screen with black letters showing for an instant, I assume that in a slow connection they will show for a longer time.
The redirect, we do not need to instruct, since the framework itself is self-correcting and will send the page to the default page (index in my case).
The comment Brian put "Otherwise if it “times out” when a user is not logged in, and you try clicking on a secure page, it just does the redirect." I have not experienced this and do not understand clearly what he means. What I have seen is that the 'time out' is measured against the value in the Session, and then it does the destroy.
You could at this point add a normal header redirect (the redirect class is still not available since I put back at the top of the init) and have even more control on where to send the person, it cold be a page designed for logged out people, that is what I have just done.
The redirect, we do not need to instruct, since the framework itself is self-correcting and will send the page to the default page (index in my case).
The comment Brian put "Otherwise if it “times out” when a user is not logged in, and you try clicking on a secure page, it just does the redirect." I have not experienced this and do not understand clearly what he means. What I have seen is that the 'time out' is measured against the value in the Session, and then it does the destroy.
You could at this point add a normal header redirect (the redirect class is still not available since I put back at the top of the init) and have even more control on where to send the person, it cold be a page designed for logged out people, that is what I have just done.