I, too, can confirm this for 2.2.12-1. I wasted two hours trying to figure out if there was *some* way to adjust my configuration to make it work, to no avail. After all, I was forced to downgrade to 2.2.11, which I was using before. Luckily I still had the packages in my cache, or I would have been doomed, as snapshot.debian.net seems to carry only rather old versions of apache2 (2.2.8 or something). Surprisingly, this issue seems to be unknown upstream, so I'm not sure if this actually occurs in upstream or is rather caused by one of the Debian specific patches in this package.
Description: This is a digitally signed message part.