possible mistake in nginx config?

[cynecx]

documentation/admin_manual/installation/nginx-root.conf.sample

Line 117 in 0ab53b5

fastcgi_split_path_info ^(.+?\.php)(/.*)$;

Shouldn't this regex be: ^(.+?\.php)(/.*|)$ instead? (If the uri has no trailing slash, fastcgi_split_path_info would fail)

cc: @jivanpal (#2197)

[ypid]

I was just debugging something and tested this. If the regex does not match, Nginx 1.18 sets $fastcgi_path_info to an empty string. You can try with:

add_header X-debug "path_info: $path_info";

I also found #795 talking about this and it worked for them. In my eyes there is no actual issue here and this can be closed.

[jivanpal]

Not sure how I missed the original notification for this, but there is indeed no issue with the regex not matching when .php is not followed by a slash. Refer, for example, to the Debian default, which is also fastcgi_split_path_info ^(.+?\.php)(/.*)$. The reason this works as desired is because of how $fastcgi_script_name is defined:

$fastcgi_script_name

request URI or, if a URI ends with a slash, request URI with an index file name configured by the fastcgi_index directive appended to it. [...] When using the fastcgi_split_path_info directive, the $fastcgi_script_name variable equals the value of the first capture set by the directive.