Welcome! Log In Create A New Profile

Advanced

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

Anonymous User
April 11, 2016 02:58PM
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
Subject Author Posted

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

Anonymous User April 11, 2016 02:58PM

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

Maxim Dounin April 11, 2016 03:44PM

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

Anonymous User April 11, 2016 04:00PM

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

B.R. April 12, 2016 12:16PM

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

Maxim Dounin April 12, 2016 12:16PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 128
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready