Conflict with Kinsta and nginx

  • I’m hosted at Kinsta and because they use nginx I wanted to have them add the rules suggested in the plugin.

    However, Kinsta support doesn’t allow all the changes – see their response below.

    How important are these rules and are there workarounds?

    
Unfortunately these lines are conflicting with our setup:
map $upstream_http_x_wp_cf_super_cache_active $wp_cf_super_cache_active {
default 'no-cache, no-store, max-age=0';
'1' 's-max-age=604800, s-maxage=604800, max-age=60';
}
more_clear_headers 'Pragma';
more_clear_headers 'Expires';
more_clear_headers 'Cache-Control';

Could you please check with the plugin developer directly to ask what exactly the code is supposed to do? As maybe there will be a workaround available from their side.

Generally, we cannot add any map or more_clear_headers directive inside the Nginx rules. So if they can let us know what the supposed goal of the code is, we can try to check in how far we can integrate it.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    Hi @loenne ,
    these rules are necessary if and only if another performance plugin interferes with the cloudflare cache with its cache-control response header for HTML pages.

    What I recommend to do, is that also written in the settings page of the plugin, is to do a test first without enabling the overwriting of the cache-control header from the web server. Only if the cache doesn’t work, enable it.

    In the next version of the plugin I will insert the option to use cloudflare workers, in this way there will no longer be any need to add any web server side rule.

    Let me know

    Thread Starter loenne

    (@loenne)

    Thanks for the reply

    I use WP Rocket – not sure if that messes with cache-control response header…

    However, it seems to work. This is the response I get when testing incognito:

    
Age: 7730
Cache-Control: s-max-age=604800, s-maxage=604800, max-age=60
CF-Cache-Status: HIT
    Plugin Contributor Salvatore Fresta

    (@salvatorefresta)

    Yes it’s working well. Check also the backend pages. You should see a BYPASS

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with Kinsta and nginx’ is closed to new replies.