I’m seeing 404/410’s mentioned, not 304’s (which are redirects).
Based on your description (disabling “serve as static”) vs the report (which still shows static autoptimize files, so .js/ .css and not .php ones), the problem is more then likely that you have a page cache that still has pages in cache that refer to the static files which have been deleted when changing AO options.
solution; after each and every change in AO also purge your page cache 🙂
hope this helps,
frank
That’s because I reenabled the ‘serve as static’ option because of that bad request.
When ‘serve as static’ is enabled, then it shows “add expired headers” in gtmetrix..
When ‘serve as static’ is disabled, then it shows 404 bad requests in gtmetrix..
You can compare the two reports attached below.
Serve as static ENABLED report: https://gtmetrix.com/reports/www.helpyoubetter.com/McOclK4F
Serve as static DISABLED report:
https://gtmetrix.com/reports/www.helpyoubetter.com/XFzqHR6M
Now the serve as static is enabled back in the site due to the above said bad requests.. That’s why I am attaching the two reports given above….
a 404 is a “file not found”, but it might be caused by some security thingie not allowing .php-files being executed from inside /wp-content/cache, maybe check you security plugin settings?
I am using All in one Wp Security plugin. Is this a problem with that all in one wp security plugin
maybe there’s option you can change in “All in one WP Security”?
