• Anonymous User 14978628

    (@anonymized-14978628)


    Hi,

    I’m using Cloudflare and noticed an issue with WebP images displaying.

    When an uncached page is visited by Edge and then the cache is generated, if i visit the now cached page with Chrome, then .jpeg images are displayed and not .webp.

    I have cache everything enabled in CF. So html is cached.

    Is it possible to display webp to supported browsers and jpeg to other browsers while using the cache everything feature in CF?

    Thanks

    p.s., i posted this question in another thread but not sure if it will be seen so creating a separate thread here.

Viewing 7 replies - 1 through 7 (of 7 total)
  • I just tested this and indeed was able to replicate it.

    In this case, I would recommend if you want to use CloudFlare in conjunction with delivering WebP files to supported browsers, to disable the Cache Everything feature and use the default settings instead.

    Thread Starter Anonymous User 14978628

    (@anonymized-14978628)

    Hi Cody, is disabling the Cache Everything feature the only solution? Perhaps it is at present, but i’m wondering if it would be technically possible at some stage for the developers to implement a fix for this?

    The Cache Everything is quite a useful feature to have as it caches the actual html file itself (the Cache Enabler cache) which significantly speeds up page loading.

    Presently, disabling the Cache Everything feature is the only solution. I will run this by the developers to see if there’s anything else that could be done.

    Thread Starter Anonymous User 14978628

    (@anonymized-14978628)

    Thanks Cody, much appreciated.

    Thread Starter Anonymous User 14978628

    (@anonymized-14978628)

    @codyarsenault

    Did you manage to speak to the developers about this issue?

    Unfortunately, this isn’t possible with CloudFlare’s Cache Everything feature. This is because when Cache Everything is enabled, CloudFlare is now caching the HTML meaning the request for the HTML doc is not reaching the origin server where Cache Enabler can determine whether or not the browser should receive the WebP or Gzipped version of the page.

    Therefore Cache Everything would need to be disabled in order to continue using WebP properly with Cache Enabler.

    Thread Starter Anonymous User 14978628

    (@anonymized-14978628)

    Ah, ok I see what you mean.

    Currently I have cache everything set as such:

    example.com/*

    Which obviously won’t work for webp for the reasons you gave.

    But what about specifying the cache enabler directory itself for cache everything so the individual html files are cached as such:

    example.com/wp-content/cache/cache-enabler/www.example.com/*

    I tried doing that but i don’t see the cf-cache-status in the response header for the post url when viewed in developer tools?

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

The topic ‘Cloudflare webP Display’ is closed to new replies.