Server and cloud settingsAccelerator for WordPress

General#

These settings allow to control server and (or) cloud caching. To check that clearance works logging of ‘Server and cloud cache updating’ should be enabled and checked there for ‘Server/cloud cache update’ items after pressing ‘Delete server’s cache (if available)’ in the operations.

• Allow cache

  It allows a page content to be cached by intermediate part of chain like server, external CDN, and clouds by setting Cache-Control directive.

• Update cache (if available)

  Currently supported ones (if specified):

  • CloudFlare

    With using special Cloudflare plugin.

  • Nginx

    With special settings or using one of special plugins:

    • Nginx Cache Controller plugin (doesn’t matter enabled ‘Enable Flush Cache’ or not)
    • Nginx Cache plugin (doesn’t matter enabled ‘Automatically flush the cache when content changes’ or not)
    • Nginx Helper plugin (doesn’t matter enabled ‘Enable Purge’ or not)
  • LiteSpeed

    Note. Only manually via ‘Delete server’s cache’.

  • Varhish

    With using special plugin.

  • Kinsta
  • Pagely
  • Pressable
  • RocketNet
  • Savvii
  • SiteGround

    With using special plugin.

    Warning. It must be enabled with disabled content optimization features (please, follow onscreen instructions) to allow controlling cache behavior. Otherwise caching will be always permanent and contains not optimized content.

    Note. It can have some timeout about a minute for rejecting repeating clearing.

  • Vimexx
  • WPEngine
  • WordPress.Com
  • EasyWP
  • O2Switch
  • CloudWays
  • DreamHost
  • GoDaddy
  • Servebolt

    With using special plugin.

NGINX#

• Method of clearing
  • No

    Clearance is disabled.

  • By 3rd party plugins

    Attempt to clean via third-party plugins (see above).

  • GET request

    Using URL for GET request and URL for GET request (all clearing).

  • Direct

    Using file deletion vis specified Cache directory.

• URL for GET request

  A custom URL for clearing cache by GET request. By default, it is site domain URL with /purge path.

• URL for GET request (all clearing)

  A custom URL for clearing all cache by GET request. If it is not set, Direct method is used.

• Cache directory

  FastCgi cache root directory. Should be got from hosting settings. You need to contact the support of your hosting if necessary.

• Cache levels

  FastCgi cache levels. Should be got from hosting settings. You need to contact the support of your hosting if necessary.

Sucuri#

• API key
• API secret