On 2015-01-13 at 21:46:01, Stefan Fritsch wrote: > Currently I can't imagine how the changes in the most recent version could > have caused this. Could you please double-check that downgrading to > 2.2.22-13+deb7u3 (still available on security.debian.org) actually fixes > the problem?
I can confirm that downgrading does NOT fix the problem. I'm starting to suspect that perhaps I had a bad config that just hadn't been applied and that the upgrade forced it to take effect when it restarted Apache. In other words, I can't reproduce the working configuration I had before the upgrade to u4, so it's probably not a bug in the apache2 package. Francois -- Francois Marier identi.ca/fmarier http://fmarier.org twitter.com/fmarier -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150131231239.gc5...@akranes.dyndns.org
