httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Slive <>
Subject Re: [users@httpd] Configuration access restriction to public_html.
Date Wed, 03 Aug 2005 16:45:28 GMT
On 8/3/05, Chris Johnson <> wrote:
> On Wed, 3 Aug 2005, Joshua Slive wrote:
> > <Location /~>
> > php_flag engine off
> > </Location>

>      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 it off everywhere.  Are you then saying it should
> be reenabled for other URLs?  Can you please give an example?

No -- notice the "~" above, which restricts applications to URLs
beginning in "~".  The advantage of using <Location> is that it is
evaluated after .htaccess files and overrides them, so it is a good
way to assure that .htaccess files are overridden.  See

In your particular case, as long as you are turning on php only for
specific directories that are not parent directories of your user
directories, then you don't really need the <Location> section, since
php will be off by default and your AllowOverride prevents it from
being turned on in .htaccess files.  The <Location> section is just an
extra guarantee.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message