WordPress Installation

Comments

4 comments

  • Austin Spires

    Hey @INNOVOT what do you mean by "not cutting the mustard"? How have you been testing these rules so far?

    To make sure that we never cache content, adding a Cache-Control: private header to the content will make sure that we never cache, and always go right to your backend. Something like:

    <FilesMatch "/wp-admin"> Header unset Etag Header set Cache-control "private no-store no-cache" </FilesMatch> ... may work for you. You only need private for Fastly, but the no-store no-cache will help to be extra safe.

  • Saima Hashimi

    Also, following doc might be helpful re: cache control headers

    https://community.fastly.com/t/suggestions-for-better-caching/250

  • Marco Corti

    [quote="aspires, post:2, topic:265"] To make sure that we never cache content, adding a Cache-Control: private header to the content will make sure that we never cache, and always go right to your backend. Something like:

    <FilesMatch "/wp-admin"> Header unset Etag Header set Cache-control "private no-store no-cache" </FilesMatch> [/quote]

    Hi, in my .htaccess I've insert code above but backend page is cached and and I keep getting errors. Could you help me? Thanks

  • Austin Spires

    @microtag since it sounds like this may involve some detailed debugging of your specific application, could you email support@fastly.com about this? I'll see the ticket as it comes in.

Please sign in to leave a comment.