That is true actually, new test system - will need to look at why 2.4.4
stumbled over that, while 2.4.x did not.
Many thanks for the feedback.
On Fri, Jun 7, 2013 at 12:00 AM, Eric Covener cove...@gmail.com wrote:
On Thu, Jun 6, 2013 at 5:56 PM, Michael Felt mamf...@gmail.com wrote:
consider
On Sun, Jun 09, 2013 at 01:52:17PM -, jaillet...@apache.org wrote:
--- httpd/httpd/trunk/modules/generators/mod_autoindex.c (original)
+++ httpd/httpd/trunk/modules/generators/mod_autoindex.c Sun Jun 9 13:52:17
2013
@@ -1840,7 +1840,7 @@ static void output_directories(struct en
I'd like to add an immutable Forbid directive to the core and use it
in some places in the default configuration instead of require all
denied.
http://people.apache.org/~covener/forbid.diff
This protects from a broad Location or If being added that
supercedes Directory/Files.
I thought someone
Is there some historical or other reason that the location has higher
precedence that directory/files? I think the other way is much more
intuitive
/* Rerun the location walk, which overrides any map_to_storage config.
*/
if ((access_status = ap_location_walk(r))) {
return
Am 10.06.2013 15:37, schrieb Eric Covener:
Is there some historical or other reason that the location has higher
precedence that directory/files? I think the other way is much more
intuitive
no - not from the daily use perspective
Directory /
Options -Indexes
Directory /
Options -Indexes -ExecCGI -MultiViews +FollowSymLinks
AllowOverride None
Require all denied
/Directory
does not mean i do not need the possibility to allow
a specific Locations/Aliases outside this and the
same for
On 10 Jun 2013, at 14:35, Eric Covener cove...@gmail.com wrote:
I'd like to add an immutable Forbid directive to the core and use it in some
places in the default configuration instead of require all denied.
http://people.apache.org/~covener/forbid.diff
This protects from a broad
Am 10.06.2013 15:58, schrieb Eric Covener:
Directory /
Options -Indexes -ExecCGI -MultiViews +FollowSymLinks
AllowOverride None
Require all denied
/Directory
does not mean i do not need the possibility to allow
a specific
On 10 Jun 2013, at 14:35, Eric Covener wrote:
I'd like to add an immutable Forbid directive to the core and use it
in some places in the default configuration instead of require all
denied.
http://people.apache.org/~covener/forbid.diff
This protects from a broad Location or If being
-Original Message-
From: Nick Kew [mailto:n...@webthing.com]
Sent: Montag, 10. Juni 2013 16:02
To: dev@httpd.apache.org
Subject: Re: Forbid directive in core?
On 10 Jun 2013, at 14:35, Eric Covener wrote:
I'd like to add an immutable Forbid directive to the core and use it
On 10 Jun 2013, at 3:35 PM, Eric Covener cove...@gmail.com wrote:
I'd like to add an immutable Forbid directive to the core and use it
in some places in the default configuration instead of require all
denied.
http://people.apache.org/~covener/forbid.diff
This protects from a broad
On 10 Jun 2013, at 15:17, Graham Leggett minf...@sharp.fm wrote:
On 10 Jun 2013, at 3:35 PM, Eric Covener cove...@gmail.com wrote:
I'd like to add an immutable Forbid directive to the core and use it in some
places in the default configuration instead of require all denied.
On Mon, Jun 10, 2013 at 10:03 AM, Reindl Harald h.rei...@thelounge.net wrote:
Am 10.06.2013 15:58, schrieb Eric Covener:
Directory /
Options -Indexes -ExecCGI -MultiViews +FollowSymLinks
AllowOverride None
Require all denied
Historically on unix it was syntactic... would you rather control access in
filepath space or uri space? It seemed pretty simple to grant location
/images read access, versus the /path/to/vhost/htdocs/images so that was
an early preference still used by some admins.
With case-insensitive
On 10.06.2013 15:37, Eric Covener wrote:
Is there some historical or other reason that the location has higher
precedence that directory/files? I think the other way is much more
intuitive
Don't know about th real motivation, but after having learned that from
the explicit description in the
Why indeed in core?
Started there because that's where AccessFileName lives.
On Monday 10 June 2013, Tim Bannister wrote:
On 10 Jun 2013, at 15:17, Graham Leggett minf...@sharp.fm wrote:
On 10 Jun 2013, at 3:35 PM, Eric Covener cove...@gmail.com
wrote:
I'd like to add an immutable Forbid directive to the core and
use it in some places in the default configuration
On Monday 10 June 2013, Plüm, Rüdiger, Vodafone Group wrote:
I'd like to add an immutable Forbid directive to the core and
use it in some places in the default configuration instead of
require all denied.
http://people.apache.org/~covener/forbid.diff
This protects from a
On Monday 10 June 2013, Eric Covener wrote:
Is there some historical or other reason that the location has
higher precedence that directory/files?
I don't know either, but I could imagine that it was just easier or
more efficient to implement in this order, considering things like
config walk
19 matches
Mail list logo
