In my previous work, I encountered that newly created websites in the nginx + php environment could not be accessed, and various errors were often caused by a single portal and some frameworks. Early nginx did not support pathinfo, but only through operations such as regular expressions, supplemented by cgi. fix_pathinfo in php. ini ,. Later I learned that this may cause vulnerabilities, as shown in this article.
In my previous work, I encountered that newly created websites in the nginx + php environment could not be accessed, and various errors were often caused by a single portal and some frameworks. Early nginx did not support pathinfo, but only through operations such as regular expressions, supplemented by cgi. fix_pathinfo in php. ini ,. Later I learned that this may cause vulnerabilities, as shown in this article.
In my previous work, I encountered that newly created websites in the nginx + php environment could not be accessed, and various errors were often caused by a single portal and some frameworks. Early nginx did not support pathinfo, but only through operations such as regular expressions, supplemented by cgi. fix_pathinfo in php. ini ,. Later I learned that this may cause a vulnerability, as described in this article, a possible security vulnerability of Nginx + PHP CGI. Now the newer version of nginx has handled this problem. As long as the configuration is appropriate, there will be no problems.
[...]