Hi,
root@test:~$ curl -I -XGET https://richiesroom.com/
HTTP/2 200
date: Mon, 20 Apr 2020 18:31:14 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d70be12bed4e21cff9fcdb563d59ea5591587407474; expires=Wed, 20-May-20 18:31:14 GMT; path=/; domain=.richiesroom.com; HttpOnly; SameSite=Lax; Secure
x-ua-compatible: IE=edge
link: <https://richiesroom.com/wp-json/>; rel="https://api.w.org/"
link: <https://richiesroom.com/>; rel=shortlink
x-litespeed-cache: hit
vary: Accept-Encoding,User-Agent
alt-svc: h3-27=":443"; ma=86400, h3-25=":443"; ma=86400, h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
x-turbo-charged-by: LiteSpeed
cache-control: max-age=259200
cf-cache-status: HIT
age: 3252
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5870f0e98d9dd65d-MAD
cf-request-id: 023a74e5f20000d65d1e832200000001
In this HTTP response header, there are 2 things you need to check
cache-control: max-age=259200
cf-cache-status: HIT
for cf-cache-status
, I believe you have understood why this happens , as if Chrome user accesses it first, CloudFlare will cache page with webp image and then Safari user accesses it , it received webp link , and page broken.
So at this point , you only have 2 options.
1. Disable CloudFlare cache which is the more appropriate approach , unless you have plugin that controls CF purge , that purges your cache when you update/publish post , otherwise your user will see out-dated content as the cache is still being served if you didn’t purge it.
2. disable webp replacement.
Second thing
cache-control: max-age=259200
this header, will instruct browser to cache your page for 3 days
Which means , if you post/edit your site , user won’t be able to see the new content in 3 days (unless this is new user who never visited your site , or who force browser cache to be disabled or cleaned it.)
Ideally , for a dynamic CMS site like WordPress, the page should have to be no-cache , as this post , it gives cache-control: no-cache, must-revalidate, max-age=0
header, so user’s browser won’t cache the page.
Best regards,
-
This reply was modified 4 years, 10 months ago by
qtwrk.
-
This reply was modified 4 years, 10 months ago by
qtwrk.