Post #1740740

@elena@aseachange.com looking at the response headers, the assets (fonts, css, js) are indeed served from cache (cdn-cache: HIT), but fedi instances don't load the assets when generating the preview, only the main HTML. The main HTML file is still not cached by the Hostinger CDN (x-hcdn-cache-status: DYNAMIC header, then a x-powered-by: PHP/8.2.30 confirming that wordpress was called). I'm not certain about the specifics for Hostinger, but in most cases, DYNAMIC indicates that the wordpress server itself denied caching via a Cache-control header. Right now, I think the stampeede issue will still happen, unless you change the wordpress config to allow caching of generated pages. It's not enabled by default, because when you enable it, you need to setup cache invalidation for page changes to propagate.