AN
Йеп
OK then, but the doubt remains:
Why is the request not being captured by the default virtualhost ?
Size: a a a
2021 April 07
HF
E
Is captured by the default virtualhost but your location internal for errors don't have a file log defined so they use the default log
HF
it does
AN
It's being captured there. But as
Requests are logged in the context of a location where processing ends. It may be different from the original location, if an internal redirect happens during request processing.- the log phase occured around /404.html, which has no access log defined - therefor default one was used.
E
Exactly
HF
not quite,
location / {
access_log /var/log/nginx/catchall.log;
return 404;
}HF
and I do have a
404.htmlE
Not, the location for the 404
E
location ~ '^/(400|401|403|404|405|429|502|503)\.html$' {
root /var/www/error;
internal;
}this one don't have a log file so they use the default log
E
when you return 404 is captured by this other location
HF
OK, we are talking about separate things here
HF
I am not interested in capturing the redirect, I want to capture what arrives to the root location, before it's redirected to the 404
E
but the logs is registered by the latest location in this case that block
HF
really ?
AN
Then you should disable error interceptions there. That's the way how it works.
HF
how should I do that ?
AN
Disable error_pages for default_server.
Or, define a log file in default_server context, not a location; as a request ends in other location than /
Or, define a log file in default_server context, not a location; as a request ends in other location than /
E
exactly the request ends in the location with the errors
HF
I had placed access_log within location because I wanted to exclude things like favicon.ico, robots.txt and so on