Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Authcache now allows you to cache for anonymous users.
How does this differ from using Boost for anonymous users?
Comments
Comment #1
simg CreditAttribution: simg commentedSo far as I can see, there isn't a difference in principle. (though there might be minor advantages either way in the implementation)
And so far as I know, Authcache has always cached for anonymous users
Comment #2
znerol CreditAttribution: znerol commentedAuthcache for anonymous users works exactly like the built-in caching mechanism of drupal core. When configured properly it is possible to avoid connecting to the database and serve pages directly from e.g. memcache. However some PHP code is still executed for each request. In contrast using boost it is possible to avoid executing PHP altogether when serving cached pages.
Comment #3
znerol CreditAttribution: znerol commentedFYI, using authcache together with boost could be an option in the future: #1932444: Boost as Authcache Backend
Comment #4
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedI have varnish enabled on a multisite setup.
So I would like to not have to enabled another module and have to edit /etc/varnish/default.vcl file to accomodate boost special http rules
Comment #5
znerol CreditAttribution: znerol commentedDon't get me wrong, boost will never be a requirement for authcache. But it could be interesting as an option - especially on shared hosts.
Comment #6
znerol CreditAttribution: znerol commentedAuthcache now has experimental support for boost as the cache backend (see authcache_boost in the modules directory of the 7.x-2.x branch).