correct, but why would that be an 'error'
an 'error' to me is something that the server needs to be reconfigured
for. this could be simple human error. it could also require server
tweaks to make it work too, but i guess you're right.
On Sat, Mar 14, 2009 at 12:46 PM, Igor Sysoev <is...@rambler-co.ru> wrote:
On Sat, Mar 14, 2009 at 11:22:06AM -0700, mike wrote:
2009/3/14 Igor Sysoev <is...@rambler-co.ru>:
Probably 403 should be return in both cases (static and dynamic) if error
is file not found.
That is fine with me. I was going to recommend that but thought it
might be a bit incorrect. Since htpasswd stuff -is- required to be
configured on the server level, it is sort of a server error if it's
pointing to the wrong file. However, the users can control the files a
lot of the time and remove them...
As long as there is a simple to read error log entry for it, that
works. Right now a 404 throws an "error" - shouldn't that be more like
a "notice" ?
This missing file should be an error as it has more to do with server
configuration. But me randomly typing in /ekfhskdfdskhfs into a site
should not raise an "error" level:
IMHO it should be less important for a 404 :)
The error level is done as in Apache. There is no simple way to tell
broken link from mistype/etc.
11 messages in ru.sysoev.nginxRe: Igor any change auth_basic_user_f...
.Other
