the '+' is standard for apache options.
it means add.  without the '+' then this would eliminate other options
except for ExecCGI.
the documentation is here:
http://www.apache.org/docs/mod/core.html#options
hth,
--
___cliff [EMAIL PROTECTED]http://www.genwax.com
Jerrad Pierce wrote:

> http://perl.apache.org/dist/cgi_to_mod_perl.html
>
> Also uses a +ExecCGI for the location, but not the file.
> It would be nice if that page documented what the + was for at least;
> if not the Apache documentation, though there is no mention of it in
>         http://www.apache.org/docs/mod/core.html#options
>
> > -----Original Message-----
> > From: Theo Petersen [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, August 01, 2000 9:43 AM
> > To: Alan E. Derhaag
> > Cc: mod_perl list
> > Subject: Re: Apache::Include requires ExecCGI on doc root?
> >
> >
> > "Alan E. Derhaag" wrote:
> > >
> > > Theo Petersen <[EMAIL PROTECTED]> writes:
> > >
> > > > I was experimenting with Apache::Include and found
> > something odd.  First
> > > > I tried a document in htdocs that used a virtual include like so:
> > > >
> > > > <!--#include virtual="/perl/hello-mod_perl.pl" -->
> > > >
> > > > This works fine, and hello-mod_perl.pl runs via Apache::Registry.
> > > >
> > > > But when I changed the include to use Apache::Include like so:
> > > >
> > > > <!--#perl sub="Apache::Include" arg="/perl/hello-mod_perl.pl" -->
> > > >
> > > > it didn't work, and I got an error in error_logs:
> > > >
> > > > [Tue Jun 27 11:22:59 2000] [error] access to
> > > > /usr/local/apache/perl/hello-mod_perl.pl failed for
> > 192.168.3.9, reason:
> > > > Options ExecCGI is off in this directory
> > > >
> > > > I verified that ExecCGI is enabled for
> > /usr/local/apache/perl (besides,
> > > > the Apache::Registry version wouldn't have worked without
> > it).  Turns
> > > > out that Apache::Include worked fine when I enabled
> > ExecCGI for htdocs.
> > > >
> > > > Is there a reason why Apache::Include requires this when
> > mod_include
> > > > doesn't?
> > >
> > > Did you ever get a responce?  I searched the archives and
> > find nothing
> > > touching upon this, otherwise.
> > >
> > > I have a similar problem and I was wondering if your httpd.conf file
> > > had either a <Directory> or <Location> entry that specified
> > `+ExecCGI'
> > > instead of `ExecCGI' as that appears to make a difference, as well.
> > >
> > No, I never got a response.  What difference does +ExecCGI make?  I
> > don't recall having it in my conf file at the time.
> >
> > ..Theo
> > --
> > Theo Petersen            mailto:[EMAIL PROTECTED]
> > "Well, let's get back to work; the world isn't going to end itself."
> >   --MST3K, "The Space Children"
> >

/


Reply via email to