Minimizing doesn’t work on my nginx with APC

[MatzeKitt]

I use a fresh Debian Stretch system with the official builds of nginx and PHP 7. My caching method is APC and it does cache some files (if I may trust the stats on the dashboard so far).

The problem is that neither the HTML nor the JavaScript minimizing is working on my system. A live demo with the current active setting “HTML + Inline JavaScript” results in a source code as usual, uncompressed: https://kittpress.com

I left every other setting untouched.

The nginx configuration is, of course, identical to the one in the wiki.

If you need any further information, please let me know.

[stklcode]

Is your live demo up to date with Cachify still active? Looks like caching does not work at all.

If it worked, the HTML code should contain the Cachify signature in the end. Should look lilke this:

<!-- 
Cachify | http://cachify.de
APC Cache @ 01.01.1970 12:34:56
-->

Did you add the corresponding lines to your php.ini (or PHP config within nginx), as described on the "Setup" tab of the Cachify settings?

[MatzeKitt]

Yes, it is.

And yes, I added the PHP configuration inside of nginx:

        ##
        # Cachify
        ##

        location ~ .php {
                include /etc/nginx/fastcgi.conf;
                fastcgi_pass 127.0.0.1:9001;
                fastcgi_param PHP_VALUE auto_prepend_file=/var/www/kittpress/wp-content/plugins/cachify/apc/proxy.php;

                location ~ /wp-admin/ {
                        include /etc/nginx/fastcgi.conf;
                        fastcgi_pass 127.0.0.1:9001;
                        fastcgi_param PHP_VALUE auto_prepend_file=;
                }
        }

You can ignore the different filename for fastcgi_params as I use this file for a custom implementation for another software.

However, I can’t find any setting I should change in the php.ini file. Did I miss something here?

I noticed this: https://wordpress.org/support/topic/plugin-has-no-valid-headerapc-caching/#post-8698598

So if this is still the current state of the plugin it can’t be used within PHP 7 because there is no more APC but OPcache and APCu.

[stklcode]

However, I can’t find any setting I should change in the php.ini file. Did I miss something here?

No, the description is just little confusing. You might as well place the auto_prepend_file value inside the php.ini (global or pool), if not passed by nginx. Should give the same result

So if this is still the current state of the plugin it can’t be used within PHP 7 because there is no more APC but OPcache and APCu.

Yes and no. The APC proxy explicitly checks for extension_loaded( 'apc' ), which should fail (you might try on your system or check the phpinfo()). If you really want to use APC(u) (I would suggest having a look at memcached), you can install apcu_bc (APC backwards compatibility) via PECL to re-enable apc_fetch() (and probably remove the extension check).

[MatzeKitt]

apcu_bc has been installed automatically (there’s an official package in Debian Stretch 🙂 ) and thus extension_loaded( 'apc' ) returns a true, so this couldn’t be the problem.

[stklcode]

I think I might just have found the bug... Your page is shipped via HTTPS and we changed the hash-function some releases ago (#2), but forgot the APC proxy.

Could you replace this line in your cachify/apc/proxy.php: && ( $cache = apc_fetch( md5( $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'] ) . '.cachify' ) ) with this: && ( $cache = apc_fetch( md5( 'https-' . $_SERVER['HTTP_HOST'] . $_SERVER['REQUEST_URI'] ) . '.cachify' ) )

[krafit]

No, the description is just little confusing. Well, it's not supposed to be confusing, isn't it? We should take care of, see #136

[MatzeKitt]

Even then, it won’t work. On the one hand function_exists('apc_cache_info') in general returns true but $cache=@apc_cache_info($cache_mode) doesn’t, which results in a different behavior of APCu according to APC.

So even with apcu_bc I can’t get APC running in a way as needed by Cachify. 😞

[stklcode]

I know the APC backend has several flaws and this issue is yet a year old, but I'd like move this out of the currently blocked release and into the 2.4 milestone with an overhauled fully APCu compatible backend.

Any other opinions on that?

[krafit]

moves issue to 2.4