> 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.
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
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
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
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
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
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 when I don't specify it at all, the