Hello @chadreitsma
Thank you for reaching out and I am happy to help!
Can you please check the Performance>Browser Cache>Advanced section and let me know if the option X-Content-Type-Options is enabled and try to toggle it (save all settings and purge the cache each time) and see which if this is the cause of the MIME type issue with those files?
Thank you!
Hey Marko,
Thanks for the quick reply!
That option is disabled – we have x-content-type: nosniff set at the server level.
I already tried disabling that, and while that did fix the nosniff warnings, the server was still reporting 500 errors on the actual files.
Digging a little deeper, I can’t even see the files that W3 is trying to serve on the server – here is an example URL: /wp-content/cache/minify/1/c1399.css (this file doesn’t exist)
I checked the file+folder permissions and they’re all normal.
-
This reply was modified 2 years, 3 months ago by
Chad Reitsma.
Hello @chadreitsma
So it seems that you are talking about the multisite. Can you confirm this?
Can you please check the .htaccess/nginx conf and make sure that the rewrite rules are the same as in the Performance>Install?
Are you using a single configuration for all sites in the multisite setup – Performance>General settings>Miscellaneous?
Thanks!
Hey Marko,
Oh yes – It’s a multisite. I double-checked all of the configs as you mentioned, and everything was correct + matching.
I decided to try a clean install. I removed the plugin, cache folder, and w3tc-config folder, then re-installed and re-configured everything. It seems to be working now, and I can see the files in the multisite minify folders! 🙂
Not sure what the actual problem was, but thank-you for your time and guidance, we appreciate it!
Cheers,
C.