autoptimize has a .htaccess-file in wp-content/cache/autoptimize/ and it is configured in such a way it only affects the autoptimized CSS/JS files.
now based on the description of http headers, it is not designed to set HTTP-headers (expiry & cache-control) for images, but to inject HTTP headers for wordpress pages/ posts/ .., so it might be you need to look of an alternative solution?
Thanks, I solved most of the cache headers by modifying htaccess directly. Also I want to report a bug, I had to deactivate this plugin because it breaks theme customization and media image display possibly because of a conflict with an existing plugin. This plugin needs a lot of optimization and compatibility work.
This plugin does not modify the cache headers of HTML documents neither their static resources. I guess you need to find some other solution.
The main goal of this plugin is to help with securing of websites and to solve some common issues with Same-origin policy.
Hi
I have the same issue with WP Super Cache, you have to delete the cache all the time before the headers change.
Caching shouldn’t have anything to do with the headers so why is this happening?
Is it this plugin or WP Super Cache?
When I test my headers with different scanners I keep getting different results despite them being set up in your plugin.
How can we solve this problem?
Cheers
Colin
Hi @cjc1867,
The problem with WP Super Cache is solved since v1.4.0 of Http Headers. You must use the Apache/htaccess method (see the Advanced settings)
Hi Dimitar
It appears that caching plugins just cache the content and nothing else so web security is not considered. Shame on them….
I have just started to add the settings to the .htaccess file after finding information on how to do it then enabled the cache and yes started to work again.
But then without knowing your fixed, updated and solved the problem all round.
Thank you for doing this as not everyone is technically minded and wouldn’t want to play with the .htaccess file as it can cause problems with your website. This will be easy now to implement web security and have cache enabled.
Cheers
Colin