Any cache plugin installed results in fastly not setting the cache headers for surrogate control.
This is frustrating as we cannot reduce the load on the server and also cannot reduce the data usage as nothing is compressed.
There are really two ways then:
1. setup a VCL to override what the host is setting but then you have to have separate values for category (arhive) landing pages, sitemap, home page and the posts itself.
2. do a custom .htaccess and remove any rules placed there by the cache plugin.
Does anyone have any advice? There does not seem to be any fastly support from any of the cache plugins and would be great if Fastly plugin either forced it or at least had support for/from the top 3 plugins so that surrogate values can be controlled.
Please sign in to leave a comment.