Unfortunately that doesn't work. I'm still getting:
[14/Mar/2009:13:24:03 +0100] [domein.com/sid#a079eb0][r
Any other ideas?
Main Topics
Browse All TopicsWhen using the core rules from Mod_security, how can i configure a rule that disables scanning for /home/phpMyAdmin without using a htaccess file or reconfiguring every vhost file on a server. The configuration file i use is (on top of the standard rules): modsecurity_crs_99_customr
I tried:
SecRule SCRIPT_FILENAME "(^/home/phpMyAdmin.*)" phase:2,log,allow,ctl:rule
But that doesn't work because the other rule is processed first and once triggered stops processing. In phase 1 the SCRIPT_FILENAME variabele doesn't seem to be available yet for processing so i cannot do it there. I also tried:
<Directory "^/home/phpMyAdmin/">
SecRuleEngine Off
SecFilterInheritance Off
</Directory>
This doesn't do anything either...
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Unfortunately that doesn't work. I'm still getting:
[14/Mar/2009:13:24:03 +0100] [domein.com/sid#a079eb0][r
Any other ideas?
The problem is solved, im posting the answer here for others to read. The problem was that the rule was enclosed in an inproperly named <ifmodule> directive which caused the rules not to fire (naturally). Having fixed that solved the problem. Although i ended up using the SERVER_NAME variable for the host header instead of a directory (since in this case it was always a subdirectory). And am using 2 files:
/etc/apache2/modsecurity_r
/etc/apache2/modsecurity_r
The first for whitelisting entire IP addresses or domains. Fires before the other rules. The second fires after the other rules and is used for handling false positives.
Business Accounts
Answer for Membership
by: caterham_wwwPosted on 2009-03-14 at 05:15:56ID: 23886415
<Directory "^/home/phpMyAdmin/">
should read
<Directory "/home/phpMyAdmin">
without the ^ since this isn't a regEx.