Andr� Malo wrote:
all in all a good work, I think. Of course ;-) some additionally
thoughts:
Thanks! I've incorporated most of your suggestions. A couple comments below.
<Files>:
I have a problem with that container (in general). It does not really
apply to files, rather the "filename-part" of the URL (which maybe the
result of an internal redirect, of course). For example:
<Files .*> Order Allow,Deny Deny From All </Files>
any requested dotfile, whether existing or not, returns a 403 with this
(and not a 404, if it does not exist).
Is this worth to be explained to the user? Or am I wrong at this point?
----
> > How the sections are merged: > > I really don't understand the technical note there, could someone > explain that to me? ;-) > > ----
These are both caused by the complex way that apache handles configuration merging internally. I don't understand it perfectly myself. Perhaps one of the developers familiar with the configuration code would like to enlighten us?
<FilesMatch \.(?i:gif|jpe?g|png)\z> ErrorDocument 404 /error/404.png </FilesMatch>
I assume that you've tested that regular expression and it works? If so, thanks for teaching me something new. I haven't looked in detail at the PCRE documentation, so I didn't realize you could do case-insensitive matching like that. That is certainly a commonly requested feature.
Joshua.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
