On 01/06/10 14:24, Eric Covener wrote:
On Tue, Jun 1, 2010 at 8:34 AM, Tim Watts wrote:
On 01/06/10 13:29, Eric Covener wrote:
I could do it better if there was a "FilesNotMatch" directive or
equivalent.
You can use the zero-width assertions like negative lookahead in PCRE
to create *Match
On Tue, Jun 1, 2010 at 8:34 AM, Tim Watts wrote:
> On 01/06/10 13:29, Eric Covener wrote:
>>>
>>> I could do it better if there was a "FilesNotMatch" directive or
>>> equivalent.
>>
>> You can use the zero-width assertions like negative lookahead in PCRE
>> to create *Match directives that are con
On 01/06/10 13:29, Eric Covener wrote:
I could do it better if there was a "FilesNotMatch" directive or equivalent.
You can use the zero-width assertions like negative lookahead in PCRE
to create *Match directives that are conceptually negated.
Ah. Any chance of an example to get me going,
> I could do it better if there was a "FilesNotMatch" directive or equivalent.
You can use the zero-width assertions like negative lookahead in PCRE
to create *Match directives that are conceptually negated.
--
Eric Covener
cove...@gmail.com
Hi,
Could do with some guru guidance :)
I'd like to only allow certain file extensions to be served without
messing up my other host based allow/deny rules.
Right now I have this in my config:
(included into both :80 and :443 virtualhost sections)
# We will explicitly allow only certain fil
