Custom Query (2297 matches)

nginx (openresty 1.21.4.1) is compiled in docker alpine 3.17, in nginx.conf in http block I have a delcaration of resolver

resolver 192.168.1.1 ipv6=off;
resolver_timeout 10s;

Sometime (aproximetly one time for week) nginx resolver behave strange. In upstream I have a name which is refreshed every 300s to the new A records. Sometime nginx does not resolve this name to new records and still resolve to old A records. In this situation reload fix the issue, but this is not a solution. This happends only for one name at a time which is refreshed.

Install nginx 1.25.0 from ​http://nginx.org/packages/mainline/debian on debian 12, get a warning "adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory" in process. And cat /etc/passwd also get "nginx:x:103:109:nginx user_{,:/nonexistent:/bin/false" Is it a bug?}

Example 1 (OK)

location / {
	root /path1;
	try_files $uri /index.html;
}

GET / - all ok, i see /index.html content GET /nofile - all ok, i see /index.html content

Example 2 (BUG)

location / {
	set $todir /path1;
	if ( $cookie_test = 1 ) {
		set $todir /path2;
	}
	root $todir;
	try_files $uri /index.html;
}

GET / - all ok, i see /index.html content GET /nofile - 404 not found. Where try_files to /index.html redirect? In log:

*1 open() "/path1/nofile" failed (2: No such file or directory)

Seems try_files directive don't works in this case. But why?