Bug#663530: apache2.2-common: ports.conf also specifies NameVirtualHost *:80

That being said please note, that NameVirtualHost itself is deprecated and not used anymore in Apache2 2.4. That's good to hear. Having to hae two things exactly in sync is always a bit weird; might as well eliminate the redundancy instead ! Eddy. -- To UNSUBSCRIBE, email to

Bug#663530: apache2.2-common: ports.conf also specifies NameVirtualHost *:80

Package: apache2.2-common Version: 2.2.22-13 Followup-For: Bug #663530 Dear Maintainer, I finally decided to work out why I was getting grumbles from apache about a NameVirtualHost *:80 directive. The only configuration I've actually got enabled (i.e. symlinked from sites-enabled/ to

Bug#684050: apache2-mpm-prefork: SuppressHTMLPreamble also discards data in the directory listing

Package: apache2-mpm-prefork Version: 2.2.22-9 Severity: normal Dear Maintainer, I was splitting up a validated index.html into README.html and HEADER.html in order to simplify access to contents of a local directory. The added HTML preamble and closing broke validation, so I looked up

Bug#588231: apache2: Haphazard permission check on symlinks (might be a Linux bug)

Package: apache2.2-common Version: 2.2.15-5 Severity: minor I use symlinks extensively, to expose fragments of my working directories (development source trees) in my userdir (all of which is subject to LDAP-based authentication). I had unwittingly set up some symlinks that went via directories

Bug#530535: apache2: Apache fails to follow symlinks via other symlinks

Sorry about the lack of reply - your mail got lost in what came while I was on holiday and I only now got back to it. I can't reproduce your problem. Are you sure all involved directories are accessible for the www-data user? I now slap myself on the fore-head - indeed, one of the directories

Bug#530535: apache2: Apache fails to follow symlinks via other symlinks

It occurred to me that the problem might be related to one of the symlinks having a name, .w/, to which Apache normally wouldn't allow access, so I tested with: ln -s ../work w; ln -s w/mine/toys toys but /~eddy/toys/ was also 403. However, /~eddy/code/ has become inaccessible too ! Yet, half

Bug#467480: apache2: default autoindex.conf uses bomb icon for file called score

Package: apache2 Version: 2.2.8-1 Severity: minor Tags: patch I saw occasional files and directories showing up with a bomb icon; I guessed they were broken symlinks or some such glitch, but closer investigation revealed no problem. Eventually, I noticed their names all ended in core and

Bug#467004: apache2: Apply IfModule to the internationalized error messages stanza of config

Package: apache2 Version: 2.2.8-1 Severity: wishlist Tags: patch The shipped apache2.conf ends (before the last two include directives) with a section dealing with internationalized error responses. This is commented out but preceded by a comment saying # The internationalized error documents

Bug#459591: apache2.2-common: Please include NameWidth=* in default IndexOptions

Package: apache2.2-common Version: 2.2.6-2 Severity: wishlist I sporadically run into web sites with directory listing enabled but can't read large parts of the file names because the site hasn't configured IndexOptions NameWidth=* or some specific value for NameWidth. The problem is

Bug#397310: our workaround

Thank you Joseph - that fixed mine, too :-) Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#397310: How do I repair my config ?

What else do I need to change to make this work ? I forgot to mention: I *did* shuffle the symlinks and when I symlinked *all* auth* into enabled, and restarted, I got: quote src=error.log [Wed Nov 08 19:50:26 2006] [notice] caught SIGTERM, shutting down [Wed Nov 08 19:50:35 2006] [notice]