The error message suggests that the user mod_perl is running under does not have permissions to read /my/handler/lib/HTTP/Config.pm so if you go up the tree from there until you find the offending directory and allow read perms for the mod_perl user that might be all that is needed. Worth a try, anyway.
Are you on a system using SELinux or AppArmor? That might also be a consideration.
🦛
In reply to Re: module not found errors in a mod_perl handler
by hippo
in thread module not found errors in a mod_perl handler
by tomgracey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |