- Issue created by @luke.leber
- 🇺🇸United States bkosborne New Jersey, USA
Just a note that if/when we implement this, we'll need a release note to indicate that the entire Cloudflare cache should be purged, because all the cache tags will have changed.
The Cloudflare purge by tag feature operates on an entire zone, not a specific domain within the zone. This proves troublesome for users that are running multiple domains in that cache invalidation can happen too liberally.
This has the potential to be very troublesome for users with dozens or hundreds of domains in one zone.
I have not manually tested this as I do not have the authority to perform this kind of zone modification. Steps to reproduce are theoretical.
example.coma.example.com and b.example.comnode_list cache tag (for example)a.example.coma.example.com was invalidated -- great! This is expected!b.example.com was also invalidated! -- ouch!This happens because the node_list cache tag is effectively colliding between the two domains.
Incorporate the site UUID or some other unique identifier into the hash calculation to ensure that cache tags are unique to the domain they're generated on.
None
None
Active
2.0
Code
Just a note that if/when we implement this, we'll need a release note to indicate that the entire Cloudflare cache should be purged, because all the cache tags will have changed.