I don’t understand
-
You responded to a message I left for @cybr (TSF).
I am on DreamHost, and I do not have CloudFlare running.
I had it (Cloudflare) running for a few weeks but simply caused endless problems and errors and it isn’t valuable enough for me to debug.
I had also turned Varnish Purge off at the same time.
I have set the object cache built into TSF as @cybr had suggested in his response to me.
The Varnish Purge is asking about IPv4 address although I understand DH doesn’t offer static IPv4 addresses.
In the error message there is a link to “erase your Varnish IP” “https://www.talkingabouteverything.com/wp-admin/tools.php?page=varnish-status#configure”
It doesn’t seem to do anything, and it doesn’t indicate httpS so I don’t know if that is an issue.
Varnish is running but cannot cache.
– I don’t see any plugin or anything that allows me to use or not use Varnish so this is confusing.
You have a Varnish IP set but you don’t appear to be using a proxy like Cloudflare or Sucuri. Please erase your Varnish IP
– I am not as noted.
– I have clicked the link and I have seen no observable changeYour site is compressing content and making the internet faster.
– ok – i’m not sure I really want to do this, but ok
A plugin or theme is setting a PHPSESSID cookie on every pageload. This makes Varnish not deliver cached pages.
– Ok is that the settings from TSF @cybr ; where should I check?
– On the other hand I know from the error that I had with TSF that the is indeed caching or I wouldn’t have had that issue.
The “Age” header is set to less than 1, which means you checked right when Varnish cleared the cache for that url or Varnish is not actually serving the content for that url from cache. Check again (refresh the page) but if it happens again, it could be one of the following reasons:
That url is excluded from the cache on purpose in the Varnish vcl file (in which case everything is working.)– When I refresh I get that same message
A theme or plugin is sending cache headers that are telling Varnish not to serve that content from cache. This means you will have to fix the cache headers the application is sending to Varnish. A lot of the time those headers are Cache-Control and/or Expires.
– is this from TSF or something else?
A theme or plugin is setting a session cookie, which can prevent Varnish from serving content from cache. You need to make it not send a session cookie for anonymous traffic.
– I would think that session cookies for anonymous traffic in my case is a meaningful feature.
Something is setting the header Cache-Control to “no-cache” which means visitors will never get cached pages.
– I know at least some stuff is getting cached
Something is setting the header Pragma to “no-cache” which means visitors will never get cached pages.
– I know at least some stuff is getting cached
- The topic ‘I don’t understand’ is closed to new replies.