Does "include" use the "configuration prefix" or the "path prefix"? (2 replies)

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

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx