404s logged in error.log?
daniel.black at openquery.com
Sat May 18 03:23:21 UTC 2013
----- Original Message -----
> I might have misread the two answers here, but I get the impression
> they're saying the exact opposite of each other.
If you analysed the responses and what you have I suspect you would of realised that I was in error and the information you have and the directive highlighted by Piotr gives you the ability to manipulate the logging to what you want.
> Here's a sample
> error message I'm seeing in error.log when doing a GET on a file that
> doesn't exist:
> 2013/05/18 02:21:27 [error] 11619#0: *417 open()
> failed (2: No such file or directory), client: 220.127.116.11,
> my.server.com, request: "GET /foo.html HTTP/1.1", host:
> Just to confirm, should I be seeing the error message above in
> error.log, or did I misconfigure something? I can see a corresponding 404 being
> logged in access.log.
A misconfigure assessment depends on what you want. The logs highlight that 404 do appear in the error log though this doesn't need to be the case ( http://nginx.org/en/docs/http/ngx_http_core_module.html#log_not_found )
More information about the nginx