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 wal
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
> > >
> > > Th
On Monday 10 June 2013, Tim Bannister wrote:
> On 10 Jun 2013, at 15:17, Graham Leggett wrote:
> > On 10 Jun 2013, at 3:35 PM, 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 a
> Why indeed in core?
Started there because that's where AccessFileName lives.
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 th
Historically on unix it was syntactic... would you rather control access in
filepath space or uri space? It seemed pretty simple to grant read access, versus the so that was
an early preference still used by some admins.
With case-insensitive filesystems it became a real problem. Granting
acce
On Mon, Jun 10, 2013 at 10:03 AM, Reindl Harald wrote:
>
>
> Am 10.06.2013 15:58, schrieb Eric Covener:
>>>
>>> Options -Indexes -ExecCGI -MultiViews +FollowSymLinks
>>> AllowOverride None
>>> Require all denied
>>>
>>>
>>> does not mean i do not need
On 10 Jun 2013, at 15:17, Graham Leggett wrote:
> On 10 Jun 2013, at 3:35 PM, 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/fo
On 10 Jun 2013, at 3:35 PM, 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 supercedes Di
> -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
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 supercedes Dire
Am 10.06.2013 15:58, schrieb Eric Covener:
>>
>> Options -Indexes -ExecCGI -MultiViews +FollowSymLinks
>> AllowOverride None
>> Require all denied
>>
>>
>> does not mean i do not need the possibility to allow
>> a specific Locations/Aliases outside t
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 Directory/Files.
>
> Options -Indexes -ExecCGI -MultiViews +FollowSymLinks
> AllowOverride None
> Require all denied
>
>
> does not mean i do not need the possibility to allow
> a specific Locations/Aliases outside this and the
> same for specific exceptions inside vho
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
Options -Indexes -ExecCGI -MultiViews +
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 ac
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 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
>
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 wrote:
> On Thu, Jun 6, 2013 at 5:56 PM, Michael Felt wrote:
> > consider this a curiosity - but using th
19 matches
Mail list logo
