cf-edge-cache response header is missing! Please clear any server cache used via other plugins.
cf-edge-cache response header is missing! Please clear any server cache used via other plugins.
cache im lokalen cache gelöscht. weitere caches benutze ich nicht.
I use the Peepso Plugin
Im logged in as Admin in Wordpress. But i cant see the Peepso Activitystream
cf-edge-cache response header is missing! Please clear any server cache used via other plugins.
i cant get the error away and i cant see the activity stream of pepso
there is no external caching
there is no external caching
Das ist definitiv nicht die Wahrheit! In den Headern deiner Seite lässt sich in der Server-Antwort folgendes finden:
via: 1.1 webcache1 (Varnish/trunk)
Ich konnte recherchieren, dass euer Hoster anscheinend one.com ist. Anscheinend benutzen die einen Cache für die gehostete Seite. Versuche einmal in die .htaccess-Datei im Quellverzeichnis deiner WordPress-Installation folgende Zeile ganz am Anfang einzufügen:
Header add “disablevcache” “true”
Wenn das nicht funktioniert, bleibt nur noch die von one.com selbst empfohlende Methode zu verwenden. Nämlich der .htaccess-Eintrag:
Header add “Cache-Control” “no-cache”
Quelle: Wie kann ich den Varnish-Cache deaktivieren?
Letztere Methode wird jedoch vermutlich auch den Cloudflare-Cache instruieren die Seiten nicht zu Cachen. Daher müsstest du dann eigene Cache-Regeln erstellen, welche die no-cache Direktive des Servers ignorieren und die Daten mit einer von dir bestimmten TTL speichern.
This looks like a server-side caching or Cloudflare integration issue, rather than a problem with the browser’s local cache. The cf-edge-cache response header needs to be added by the site’s caching/CDN configuration, so clearing the local browser cache alone would not necessarily resolve it.
I would check whether Cloudflare’s caching settings are enabled correctly and whether another WordPress caching or optimization plugin is modifying the response headers. If you’re using a caching plugin, temporarily disabling its page-cache/CDN features can help identify a conflict.
You can also test the site with Cloudflare temporarily bypassed or check the response headers using your browser’s Developer Tools → Network tab. If cf-edge-cache is still missing, the issue is likely with the server/Cloudflare configuration rather than your local browser.
This looks like a server-side caching or Cloudflare integration issue, rather than a problem with the browser’s local cache. The cf-edge-cache response header needs to be added by the site’s caching/CDN configuration, so clearing the local browser cache alone would not necessarily resolve it.
I would check whether Cloudflare’s caching settings are enabled correctly and whether another WordPress caching or optimization plugin is modifying the response headers. If you’re using a caching plugin, temporarily disabling its page-cache/CDN features can help identify a conflict.
You can also test the site with Cloudflare temporarily bypassed or check the response headers using your browser’s Developer Tools → Network tab. If cf-edge-cache is still missing, the issue is likely with the server/Cloudflare configuration rather than your local browser.
I’ve dealt with similar website configuration considerations while working on imaLimousine Service, where reliable website performance is important for customers looking for chauffeur and airport transfer services: Limousine Service Zurich | Premium Chauffeur & Airport Transfers
