Hello,
first of all I'd like to say that litespeed works really nice for me, in the last 5 days I migrated 2 servers to it (from a strange lighttpd setup and a productive apache2.0), because I could not find a configuration for Apache that doesn't kill Apache under high load.
I am using Litespeed 3.0 Enterprise Beta with the trial key and loading the Apache configuration worked fine. However, some VHosts had a password protection on them although no .htaccess created an authentication realm. After some Apache-config reading I found the problem:
diroptions.conf, included from my main config:
<web2-domain>/webalizer/ should have been password protected, but <web2-domain>/ not - but it and all other subdirs were.
I'd be happy to supply more information to help you identifiy this bug (it seems to be one).
Gonna continue enjoying my new-and-very-speedy lshttpd,
Christian
first of all I'd like to say that litespeed works really nice for me, in the last 5 days I migrated 2 servers to it (from a strange lighttpd setup and a productive apache2.0), because I could not find a configuration for Apache that doesn't kill Apache under high load.
I am using Litespeed 3.0 Enterprise Beta with the trial key and loading the Apache configuration worked fine. However, some VHosts had a password protection on them although no .htaccess created an authentication realm. After some Apache-config reading I found the problem:
diroptions.conf, included from my main config:
Code:
<Directory "/var/www/localhost/web2/html/webalizer/">
AuthType Basic
AuthName "Restricted Area"
AuthUserFile /etc/apache2/vhosts.d/htpasswd/2-5-47ebb31d82b1e8d4add673589ec7e7b2.htpasswd
require valid-user
</Directory>I'd be happy to supply more information to help you identifiy this bug (it seems to be one).
Gonna continue enjoying my new-and-very-speedy lshttpd,
Christian