5
I found the no-cache HTTP header commands for the browser not to cache pages in the header.php file in the XOOPS main directory. So browsers should not cache any XOOPS page that include the root header.php file.
However, there are instances where you may call the redirect_header() function BEFORE including the header.php file in the root directory. This commonly occurs when you check if the user is logged in at the start of your module code like this Quote:
if ( !$xoopsUser ) {redirect_header(...)}
include $xoopsConfig['xoops_url']."/header.php";
... continue with the module code...
The problem is that the redirect_header() function does not have the HTTP no-cache commands. Therefore, the browser caches the redirect page. This has caused me many problems with users not being able to access pages even when they have permission to do so.
My suggestion would be to include the PHP header() function with the no-cache and expire commands in the redirect_header() function as well.
Otherwise, you will need to go through all the files to makes sure that $xoopsConfig['$xoops_url']."/header.php" appear before your redirect_header() call to avoid browser cache problems.
