• Resolved nikkers

    (@nikkers)



    Cloudflare Zone ID and API Token was set up for a free Cloudflare account, with the terminal command test saying it was working – however is this correct in the Help Options?

    webpc_cloudflare_cache_config: false

    Thank you

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    Hi @nikkers,

    Thank youi for your message.

    The webpc_cloudflare_cache_config value will be correct for paid Cloudflare. The webpc_cloudflare_cache_purge value indicates whether it was possible to successfully connect to the Cloudflare API – it should be true even for free Cloudflare.

    Best,
    Mateusz

    Thread Starter nikkers

    (@nikkers)

    1. we have: webpc_cloudflare_cache_purge: yes
      So it has successfully connected to the Cloudflare API. Thanks!
    2. So for webpc_cloudflare_cache_config it states 403. “webpc_cloudflare_cache_config: 403”. This means for a free Cloudflare account it is always getting the images from the origin server?
    Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    Thank you for your answer @nikkers!

    If you are a Pro, Business or Enterprise Cloudflare’s customer, you will be able to use our plugin with active Cloudflare CDN Caching.

    For Cloudflare free plans, our plugin will disable Cloudflare CDN Caching (but images in WebP and AVIF format will be displayed correctly). The Cache-Control header will be set to private. This is because in the Cloudflare free plans does not support the Accept header (read more). Available “Vary for Images” in your Cloudflare plan is necessary to use Cloudflare CDN Caching when loading WebP and AVIF files.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘webpc_cloudflare_cache_config: false’ is closed to new replies.