<html><head/><body>I'm using ISPConfig3 and the default nginx vhost configuration template<br>
includes the following:<br>
<br>
location ~ \.php$ {<br>
try_files /dcc5f1e779623ed233ada555c6142e42.htm @php;<br>
}<br>
<br>
location @php {<br>
try_files $uri =404;<br>
include /etc/nginx/fastcgi_params;<br>
fastcgi_pass unix:/var/lib/php5-fpm/web2.sock;<br>
fastcgi_index index.php;<br>
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;<br>
fastcgi_intercept_errors on;<br>
}<br>
<br>
What is the point of the first location block? Wouldn't the end-result<br>
be exactly the same if the content of the second block were to be moved<br>
into the first block, and the second block eliminated? For example:<br>
<br>
location ~ \.php$ {<br>
try_files $uri =404;<br>
include /etc/nginx/fastcgi_params;<br>
fastcgi_pass unix:/var/lib/php5-fpm/web2.sock;<br>
fastcgi_index index.php;<br>
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;<br>
fastcgi_intercept_errors on;<br>
}<br>
<br>
Everything "works" just fine; I'm simply curious if there is some<br>
non-obvious reason for this "try_files trick" with a file that will<br>
never exist (that HTML file doesn't exist and seems to have a<br>
randomly-generated name -- presumably to ensure that it will *never* exist).<br>
<br>
Perhaps this file is created in "Maintenance Mode", thereby causing all<br>
requests to be redirected to the maintenance message page?<br>
<br>
Thanks!<br>
<br>
-Ben<br>
</body></html>