I did not have a problem with includes working. My problem that all
these warning messages were being written to the error log. In order for
includes to work, you need the following in your httpd.conf file:
The Options directive after the directive that defines
your Document Root must have Inc
Dang.. I'm having problems getting includes to work for ANYTHING, not
just perl. I'll keep poking. Maybe sombody will respond
with a tidbit of info.
Thanks!On 8/2/05, Malka Cymbalista <[EMAIL PROTECTED]> wrote:
I never got an answer but I figured out what the problem was. In the section I adde
I never got an answer but I figured out what the problem was. In the
section I added
Options +ExecCGI +Includes
Malka Cymbalista
Webmaster, Weizmann Institute of Science
[EMAIL PROTECTED]
08-934-3036
>>> [EMAIL PROTECTED] wrote on 02/08/2005 16:00:
> Did you ever find a solution to this? I'
Did you ever find a solution to this? I'm having the same
problem, even though I've gone through and checked all the Directory
blocks to make sure either +Includes or +IncludesNoExec is active.On 7/18/05, Malka Cymbalista <[EMAIL PROTECTED]
> wrote:I just installed Apache 2.0.54 together with mod_
I just installed Apache 2.0.54 together with mod_perl 2.0.1 on a un
Solaris machine and I am getting lots of the following warnings in my
error log:
mod_include: Options +Includes (or IncludesNoExec) wasn't set, INCLUDES
filter removed
What does this mean and can I get rid of the warnings. I notic
