we provide WordPress hosting and as part of our package we shall be including Fastly. At present we are trying to understand Fastly and how best to configure it for these type of instances. We control our backend origin servers that are running Apache 2.4, PHP 5.6 and Mod_PageSpeed. Would welcome feedback on cache settings are what we are using at present
<FilesMatch "\.(html|htm)$"> Header unset Etag Header set Cache-control "max-age=0, no-cache, no-store" </FilesMatch> <FilesMatch "\.(jpg|jpeg|gif|png|js|css)$"> Header unset Etag Header set Cache-control "public, max-age=600" </FilesMatch>
do not really appear to be cutting the mustard. Aswell, we would also like to understand how we can completely bypass Fastly for the WordPress /wp-admin area ? That would be better going straight through to origin instead of the cache.
Grateful for any and all help.
Please sign in to leave a comment.