> /var/www/xxx/.htaccess: Options not allowed here
>
> I thought I had configured this correctly to allow this directive, but
> that's been a very long time any maybe Apache has changed since then.
> After reading the documentation about AllowOverride, I guess I need
> something more like this:
It
> On 18 Jun 2017, at 23:41, Frank wrote:
>
> Nigel,
>
> The point is that the default value changed for 2.3 (and hence 2.4), and you
> seem to be missing it, yes.
>
> As for why that change was made, the development mailing list might be better
> suited for that thread.
No Frank, I'm not mis
On 18/06/17 08:22 PM, Nigel Peck wrote:
On 18/06/2017 18:01, Frank wrote:
As per http://httpd.apache.org/docs/current/mod/core.html#allowoverride :
Default:AllowOverride None (2.3.9 and later), AllowOverride All
(2.3.8 and earlier)
I'm not sure what your point is. I am aware of that an
On 18/06/2017 18:01, Frank wrote:
> As per http://httpd.apache.org/docs/current/mod/core.html#allowoverride :
>
> Default:AllowOverride None (2.3.9 and later), AllowOverride All
(2.3.8 and earlier)
I'm not sure what your point is. I am aware of that and it supports the
point I am making i
On 18/06/17 06:16 PM, Nigel Peck wrote:
On 18/06/2017 16:38, Frank wrote:
You probably have another block that has AllowOverride
set, for the / path or another. Inspect all files shipped by CentOS,
and the ones you modified.
I only have one config file, since I merged all of the others in t
On 18/06/2017 16:38, Frank wrote:
You probably have another block that has AllowOverride set,
for the / path or another. Inspect all files shipped by CentOS, and the
ones you modified.
I only have one config file, since I merged all of the others in to it
that I needed. I already double chec
On 18/06/17 05:17 PM, Nigel Peck wrote:
Hi,
According to the documentation[1], the default for `AllowOverride` is
`None`, and when `AllowOverride` is set to `None`, .htaccess files are
not read at all.
When I set `AllowOverride` to `None` explicitly, I find that is the
behaviour I see, but w
2.4 has this:
http://httpd.apache.org/docs/current/mod/core.html#allowoverridelist
On Sun, Oct 13, 2013 at 1:55 AM, Toomas Aas wrote:
> Hello Pol!
>
>
>>
>> Options Indexes FollowSymLinks MultiViews
>> AllowOverride None
>> Order allow,deny
>> allow from all
>>
Hello Pol!
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
With AllowOverride setted to none, .htaccess has ignored.
For instance, if I'll want permit the use of .htaccess only about
mod_rewrite or only about ErrorD
As I said this should work and AllowOverride for / should be set to none.
The only explanation is that you are using Apache version 2.0 where
"AllowOverride Fileinfo" doesn't apply to Rewrite statements. See the
difference between 2.0 and 2.2:
http://httpd.apache.org/docs/2.0/mod/core.html#allowov
>From my understanding, if you put AllowOverride None , then you are
instructing Apache to not allow any htaccess file to be respected.
This will be affected by all your .htaccess files since you have it
in the directory directive. Chance it to AllowOverride All for
.htaccess to start kicking in.
Hello world,
am i the only one with this trouble?
br
congo thomas
On Tue, January 17, 2012 13:52, congo thomas wrote:
> I am having the set to None for allowoverride.
> My problem persists in having this set:
>
>
> ...
>
> AllowOverride FileInfo
> ...
>
>
> - following restart apache, and t
I am having the set to None for allowoverride.
My problem persists in having this set:
...
AllowOverride FileInfo
- following restart apache, and then (executed as website-user in this case):
$ touch /var/www/website/.htaccess
$ chmod 644 /var/www/website/.htaccess
$ cat "
RewriteEngine On
Re
This should absolutely work. From the documentation:
For security and performance reasons, do not set AllowOverride to anything
other than None in your block. Instead, find (or create) the
block that refers to the directory where you're actually
planning to place a .htaccess file.
What is exact
14 matches
Mail list logo
