Does "include" use the "configuration prefix" or the "path prefix"?

hroku003 at hroku003 at
Mon Apr 11 18:52:25 UTC 2016

I've read the documentation and it implies the "path prefix" would be used for the "include" directive.

Example: "include  mime.types"

However, in practice, the "configuration prefix" is always used even if the file is found within the "path prefix".
Is this the correct behaviour? 

Here are sample values:

    nginx path prefix:          "/tmp/app"
    nginx binary file:          "/tmp/app/progs/nginx/sbin/nginx"
    nginx configuration prefix: "/tmp/app/progs"
    nginx configuration file:   "/tmp/app/progs/nginx.conf" 

(I used 1.8.1 and 1.9.14.)

- diego

More information about the nginx mailing list