Problem/Motivation

I recently upgraded drupal/purge from 3.0 to 3.2 on my drupal site (drupal/core 9.2.7). The site is housed on acquia and we use acquia_purge, as well. Immediately after the upgrade, non-authenticated users (those on the other side of our varnish cache) started seeing stale content; i.e. changes to pages were not propagating out to the cache. I was able to flush the cache manually on a page-by-page basis.But on the whole, the cache invalidation seemed to be broken.

I just rolled back drupal/purge to version 3.0 and this seems to have fixed the problem.

I am in no way at all an expert in how caching works in drupal. Please feel free to ask for any relevant details that I have omitted.

I hope this report is useful.

Comments

mefron created an issue. See original summary.

bpizzillo’s picture

bpizzillo commented

This sounds like this may be related to https://www.drupal.org/project/purge/issues/3094343.

emerham’s picture

emerham commented
Related issues: +#2976480: Do not send Cache-Tags header if Cache-control: no-cache

I believe this is all related to the new logic introduced in 3.1 that used the Internal Dynamic Page Cache module and any page that is marked as 'Uncacheable' by that module no longer was purging. If this is the case then this issue is related to that.
I'm going to mark this as related to #2976480: Do not send Cache-Tags header if Cache-control: no-cache as that issue appears to be tackling it.

emerham’s picture

emerham commented
Status: Active » Closed (duplicate)