On 8/4/05, Chris Johnson <[EMAIL PROTECTED]> wrote:
> > (But be careful; There are other ways to activate php including AddHandler.)
>
> Right. This particular server is still 1.3 at themoment but may
> change soon.
>
> So AddHandler and maybe SetHandler and possibly some others. Ca
On Wed, 3 Aug 2005, Joshua Slive wrote:
> On 8/3/05, Chris Johnson <[EMAIL PROTECTED]> wrote:
> > Now, when I did this once before (it was a while ago) the
> > FileInfo override was what stopped .htaccess from doing AddType, yes?
> > That not being there is what does it. Right?
>
> Yes. Se
On 8/3/05, Chris Johnson <[EMAIL PROTECTED]> wrote:
> Now, when I did this once before (it was a while ago) the
> FileInfo override was what stopped .htaccess from doing AddType, yes?
> That not being there is what does it. Right?
Yes. See the "Override" line at
http://httpd.apache.org/docs
On Wed, 3 Aug 2005, Joshua Slive wrote:
> On 8/3/05, Chris Johnson <[EMAIL PROTECTED]> wrote:
> > On Wed, 3 Aug 2005, Joshua Slive wrote:
> > >
> > > php_flag engine off
> > >
>
> >
> > For Apache PHP module, which we have. Not used to using Location
> > much. I only want to prevent its
On 8/3/05, Chris Johnson <[EMAIL PROTECTED]> wrote:
> On Wed, 3 Aug 2005, Joshua Slive wrote:
> >
> > php_flag engine off
> >
>
> For Apache PHP module, which we have. Not used to using Location
> much. I only want to prevent its use in usr's public_html remember.
> The above would turn
On Wed, 3 Aug 2005, Joshua Slive wrote:
>
So now we know why I was confused.
> If you have php turned off by default, then the AllowOverride
> directive should prevent .htaccess files from being used to turn it on
> again. But you may want to add something like
>
>
> php_flag engine of
On 8/3/05, Chris Johnson <[EMAIL PROTECTED]> wrote:
> We need to prevent users with URLs of the ~ variety from
> doing PHP or other things which execute arbirtary code. But (there's
> always a but), at the same time we need to allow it for URLs not of
> that type, i.e. all other references.
Hey all,
We need to prevent users with URLs of the ~ variety from
doing PHP or other things which execute arbirtary code. But (there's
always a but), at the same time we need to allow it for URLs not of
that type, i.e. all other references. There's the following snippet
from httpd.conf
