This behavior is because in 2.0, proxy.load and proxy.conf contained the "LoadModule disk_cache_module" and the mod_disk_cache config. Not enabling mod_disk_cache on upgrades would break caching for proxies (debian bug 407171).
Maybe enabling mod_disk_cache on upgrades only if something like
This behavior is because in 2.0, proxy.load and proxy.conf contained the "LoadModule disk_cache_module" and the mod_disk_cache config. Not enabling mod_disk_cache on upgrades would break caching for proxies (debian bug 407171).
Maybe enabling mod_disk_cache on upgrades only if something like
egrep -iq '^[[:space: ]]*cacheenable' /etc/apache2/ apache2. conf /etc/apache2/ mods-enabled/ * /etc/apache2/ sites-enabled/ * /etc/apache2/ conf.d/ * /etc/apache2/ httpd.conf
(in preinst) gives true would be better.