/.well-known/ location in nginx configuration is too generic

Site Feedback
1

Recently I ran some Docker apps being reverse-proxied behind nginx and these apps use files and directories located in their /.well-known/ directory. However, the Virtualmin nginx snippet:

	location ^~ /.well-known/ {
		try_files $uri /;
	}

was intercepting the port forwarding to the apps and I had to change it to make it more precise:

    # do not intercept app /.well-known endpoint
    # location ^~ /.well-known/ {
    location ^~ /.well-known/acme-challenge/ {
		try_files $uri /;
	}

So as a feature request, would it be possible to use the more accurate
location ^~ /.well-known/acme-challenge/ ?