Updated to apache 2.4... argh

[Lewis]

OK, I updated my system with a bunch of stuff, including apache24 which
is working just fine, for my main site and a couple of vhosts, but not
for most.

The main virtualhost which I have defined in extras/httpd-vhosts.conf
works. I have a squirrelmail setup in users/squirrelmail.conf which also
works. Then I have a wordpress install that is installed in
users/<domain>.conf and it doesnt load at all.

A bit munged:

# cat extra/httpd-vhosts.conf
# Virtual Hosts
#
# Required modules: mod_log_config

# Please see the documentation at
# <URL:http://httpd.apache.org/docs/2.4/vhosts/>
# for further details before you try to setup virtual hosts.
#
<VirtualHost *:80>
ServerName www.*munged*.net
ServerAlias *munged*.net
DirectoryIndex index.php
DocumentRoot /usr/local/www/*munged*/
</VirtualHost>
---EOF

# cat users/squirrelmail.conf
<virtualhost *:80>
Servername sm.*munged*.net
DirectoryIndex index.php
DocumentRoot /usr/local/www/squirrelmail/
<Directory "/usr/local/www/squirrelmail">
Options Indexes MultiViews FollowSymLinks ExecCGI
Require all granted
</Directory>
</VirtualHost>

And this VirtualHost works:

# more users/vhost1.conf

<VirtualHost *:80>
ServerName www.vhost1.com
ServerAlias vhost1.com
DocumentRoot /usr/local/www/vhost1.com/
DirectoryIndex index.htm
<Directory "/usr/local/www/vhost1.com/">
Require all granted
</Directory>
</VirtualHost>

This one does not, and gives me a ERR_CONTENT_DECODING_FAILED when I try
to load it, but the page was working fine under apache22 a few hours ago
and has not been touched. It's a wordpress install (but so is the main
default site).

<VirtualHost *:80>
ServerName www.vhost2.info
ServerAlias vhost2.info
DocumentRoot /usr/local/www/vhost2.info/wordpress/
<Directory "/usr/local/www/vhost2.info/wordpress/">
AllowOverride all
Require all granted
</Directory>
<VirtualHost>

I did notice that apache2.4 seems to require *:80, so I had to change
all my directives from apache22's <VirtualHost *>.

(I don't know if all the <Directory ...>'s are needed, I put them in in
the course of trying to debug various failures.

[patpro ~ patrick proniewski]

Post by Lewis
OK, I updated my system with a bunch of stuff, including apache24 which
is working just fine, for my main site and a couple of vhosts, but not
for most.
The main virtualhost which I have defined in extras/httpd-vhosts.conf
works. I have a squirrelmail setup in users/squirrelmail.conf which also
works. Then I have a wordpress install that is installed in
users/<domain>.conf and it doesnt load at all.

that would be great if you could provide us with error.log lines related
to the failure of apache to load the faulty vhost config file...

patpro

[Lewis]

Post by patpro ~ patrick proniewski

Post by Lewis
OK, I updated my system with a bunch of stuff, including apache24 which
is working just fine, for my main site and a couple of vhosts, but not
for most.
The main virtualhost which I have defined in extras/httpd-vhosts.conf
works. I have a squirrelmail setup in users/squirrelmail.conf which also
works. Then I have a wordpress install that is installed in
users/<domain>.conf and it doesnt load at all.

that would be great if you could provide us with error.log lines related
to the failure of apache to load the faulty vhost config file...

There was no error in the logs, only the browser showing there is an
encoding error. but as I said, it worked unmodified in apache 2.2
earlier in the evening.

Looking at the site, some of the files had CRLF line endings. This
seemed to cause 2.4 to blow up. Since some people are clueless windows
users and are likely to upload RLF files again in the future, can I get
apache 2.4 to understand these line endings in addition to normal line
endings?