• Affected App
    WoltLab Suite Core

    I'm using WoltLab Suite 3.0.0 RC 2 on a CentOS 7.3 server (under WHM 60), running Apache/2.4.23 (cPanel) and PHP 5.5.38.

    I installed redis from source, then installed the redis 3.1.0 PECL extension through WHM, restarted apache, and chose "use redis" under Confiiguration > General > Cache. When I run redis-cli monitor through ssh and navigate around the site, I can see that redis is being accessed.

    But when I click on the "cache" link under "Management" in the ACP, I don't go to the cache-list page (/acp/index.php?cache-list/) any more like I used to when I was using the filesystem as the cache provider; now I get redirected to the front page of the site instead.

    I posted to the help forum to ask if this was normal behavior, and jens1o responded and said it was not. He suggested that I try clearing my browser's cache and manually deleting the cache on the server, which I did (as to the filesystem cache: I left the cache folder in web root, but deleted all files except the .htaccess file). He suggested that if that didn't fix the issue, I should submit a bug report.

    Is this something I should be concerned about? The site seems to function as it should, but I don't know how to refresh the cache (or if I even need to do so; I've never used redis before).

  • The issue is caused by a faulty redis extension, yielding an error that is intercepted by the webserver and passed back to PHP, but this time with falsified request headers. The bad request data then causes the software to redirect to display the landing page as none of the request data was suitable to determine the proper page.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!