Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I just switched from Apache2 prefork to worker and some strange problems with .htaccess, one of which is that suddenly all of my deny from <ip> directives in .htaccess, which I use to block hackers, bots, etc., are throwing 500 errors. my apache site config has the following:

    <Directory /home/me/www/>
            Options FollowSymLinks ExecCGI
            AllowOverride All
            Order allow,deny
            allow from all
    </Directory>

and then I just add lines like this:

deny from 111.222.333.444

to .htaccess; it was working in prefork, and I guess it's still 'working', since a 500 error means they probably can't access the site, but OSSEC doesn't like it, sending me emails on every 500 error. Is there any reason why it is throwing 500 errors instead of 403 errors?

share|improve this question
    
Should be something in Apache's error log when a 500 is thrown - anything useful in there? –  Shane Madden Feb 3 '12 at 4:54
    
Yes, show us Apache's log, because HTTP 500 is definitely not correct behaviour. –  Ency Feb 3 '12 at 7:29
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.