Apache::RefererBlock is forbidding all of its configuration directive from
being in .htaccess files with this:
req_override => 'RSRC_CONF'
take a look at Makefile.PL to see it.
you will want to change this to something that enables you to call it from
.htaccess files, like ACCESS_CONF. Keep in mind, though, that you'll
probably have to add DIR_CREATE and DIR_MERGE sections as well so that
things will merge properly if you plan on placing them within
directory-esque directives. Apache::Dispatch has examples of all these to
use as a guide, if it helps...
HTH
--Geoff
-----Original Message-----
From: Robert Landrum
To: [EMAIL PROTECTED]
Sent: 2/20/01 7:05 PM
Subject: htaccess files and modules
I am having difficulty reading configuration commands from a .htaccess
file.
I've modified Apache::RefererBlock so that it no longer shows a
forbidden error, but rather redirects a default URL. I need this to
apply to specific directories, but do not want the hassle of having
to modify the configuration for every directory. My goal is to place
the configuration information into the .htaccess files within said
directories. However, when I do this, I get the following error:
/www/test/.htaccess: RefBlockMimeTypes not allowed here
I'm not 100% sure how Apache::ModuleConfig works, but I'm guessing
that it simply iterates through all the configuration parameters and
checks to see if a sub by that name exists in the caller package. If
so, it calls that sub.
Perhaps this is not the correct module to use. I've read through the
Eagle book and have found obscure references to DIR_MERGE and
DIR_CREATE, but I don't understand the purposes behind these entirly.
I've also read about Apache::CmdParms, but I don't know how that
differs from Apache::ModuleConfig.
If someone could point me to a doc explaining how to permit custom
config params in .htaccess files, I would greatly appreciate it.
Thanks,
Robert Landrum
--
"Only two things are infinite: The universe, and human stupidity. And
I'm not
sure about the former." --Albert Einstein
