Log path is inherited from custom error page location

[dkanavis@…]

Hello.
It may be not truly a bug but it seems like an annoying configuration problem that has no point but causes troubles.

If you make a virtual host with separate access/error logs for different locations and one default access/error log, and then add custom error pages with their own locations, like:

access_log /var/log/nginx/my_site/access.log;
error_page 404 /404.html;
location = /404.html {
   root /www/my_site/error_pages;
}
location /static {
    access_log /var/log/nginx/my_site/static_access.log;
}

logger will write to default access log while you get an error in some specific location with it's custom log (in example, if we get 404 at /static/mistak.html, corresponding row will be added to access.log instead of static_access.log which looks logically correct).

[Maxim Dounin]

Access logs are written in the context of the location which was used to process the request at the request completion. In the particular configuration request processing ends up in the location = /404.html due to the error_page configured, and hence the default access log is used.

If you want custom access log to be used for 404 errors in the particular location, consider either not configuring error_page at all, or using a custom error_page with the same access log configured.