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

[hroku003 at yahoo.com]

THank you very much for confirmation.
Is this documented anywhere?


I looked at various places:
http://nginx.org/en/docs/ngx_core_module.html#include
http://nginx.org/en/docs/switches.html
https://www.nginx.com/resources/wiki/start/topics/tutorials/installoptions/
and I could not find it. (I also tried reading the C source, 
https://github.com/nginx/nginx/blob/master/src/core/ngx_conf_file.cbut got lost due to my lack of C experience.)
- diego


On Monday, April 11, 2016 2:43 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
Hello!

Yes, this is correct behaviour.  Configuration-specific paths like 
in the "include" directive are resolved relative to the conf prefix, 
that is, relative to the directory where nginx.conf file resides.

-- 
Maxim Dounin
http://nginx.org/

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