On Wed, 18 Sep 2013, Matthew Gabeler-Lee wrote: > >$ sudo a2enmod access_compat > > > >Then try again? If that helps, I’ll just call that from > >the postinst maintainer script, like we do in FusionForge. > > First thing I checked, but that module was already enabled, I think by > the default install, or possibly by phpmyadmin, which was the only > other apache package I had installed at that point.
Hm, “fun” (not). > This is not the first time I've seen access_compat fail to work as > expected, though I'm not sure if that's a bug, or a limitation in the > module. Indeed, I’ve recently seen something similar, where I had to use one of these new directives in exactly *one* directory in *one* vhost, whereas it worked everywhere else. I’m puzzled by it. Since the bug occurs for you but not for me, can you try patching the file until it works for you too, then send that for inclusion? That would be much appreciated. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
