One reason IIS fails to start Gzip: conflict by conflict resolution
- 2020-05-06 12:02:30
- OfStack
But there is a server did not succeed, found the reason, did not find, today suddenly thought of a side, hurriedly start to try, as expected the reason is this.
Gzip is a popular file compression algorithm, which is now widely used. When Gzip is applied to compress a plain text file, the effect is very obvious, which can reduce the file size by more than 70%. The Gzip compression algorithm is used to compress the web content and then transfer it to the client browser. The most obvious benefit is that it can speed up the loading of web pages. In addition to saving traffic and improving the user's browsing experience, there is also a potential benefit that Gzip has a better relationship with the crawling tools of search engines. For example, Google can retrieve web pages faster than normal manual crawling by reading gzip files directly. These benefits are not limited to static content. ASP, ASPX, PHP dynamic pages, and other dynamically generated content can be compressed using Gzip, along with other performance tuning mechanisms and the corresponding server-side caching rules, which can greatly improve the performance of a website.
First, the server environment: Windows2003+IIS+PHP+ISAPI Rewrite, there is no problem to check the configuration content of iis, but the status of HTTP is not opened Gzip state, today, when accessing an Discuz forum on the server, the bottom line of information: Gzip On. Flash of light, is PHP's own Gzip and IIS's conflict? Open the PHP configuration file, close php_zip.dll extension, and restart IIS.
After the above operation, check the status, and now Gzip is on. There is no problem with the original batch file opened by Gzip, the problem is that PHP also opened Gzip, IIS conflicts when opened again. It also illustrates another problem that PHP.ini has a higher processing priority than Metabase.xml.
Article from: friends together
Gzip is a popular file compression algorithm, which is now widely used. When Gzip is applied to compress a plain text file, the effect is very obvious, which can reduce the file size by more than 70%. The Gzip compression algorithm is used to compress the web content and then transfer it to the client browser. The most obvious benefit is that it can speed up the loading of web pages. In addition to saving traffic and improving the user's browsing experience, there is also a potential benefit that Gzip has a better relationship with the crawling tools of search engines. For example, Google can retrieve web pages faster than normal manual crawling by reading gzip files directly. These benefits are not limited to static content. ASP, ASPX, PHP dynamic pages, and other dynamically generated content can be compressed using Gzip, along with other performance tuning mechanisms and the corresponding server-side caching rules, which can greatly improve the performance of a website.
First, the server environment: Windows2003+IIS+PHP+ISAPI Rewrite, there is no problem to check the configuration content of iis, but the status of HTTP is not opened Gzip state, today, when accessing an Discuz forum on the server, the bottom line of information: Gzip On. Flash of light, is PHP's own Gzip and IIS's conflict? Open the PHP configuration file, close php_zip.dll extension, and restart IIS.
After the above operation, check the status, and now Gzip is on. There is no problem with the original batch file opened by Gzip, the problem is that PHP also opened Gzip, IIS conflicts when opened again. It also illustrates another problem that PHP.ini has a higher processing priority than Metabase.xml.
Article from: friends together