However, one server was not successful. I found the cause and did not find it. Today, I suddenly thought of one aspect. The reason is that I tried it quickly.
Gzip is a popular File compression algorithm. It is widely used nowadays. When Gzip is used to compress to a plain text file, the effect is very obvious, it can reduce the file size by more than 70%. Use the Gzip compression algorithm to compress the webpage content and then transfer it to the client browser. In this way, the compression actually reduces the number of bytes transmitted over the network. The most obvious advantage is that it can speed up webpage loading, in addition to saving traffic and improving the user's browsing experience, another potential benefit is that Gzip has a better relationship with search engine crawling tools. For example, Google can directly read gzip files to retrieve webpages faster than normal manual crawlers. These benefits are not limited to static content. ASP, ASPX, PHP dynamic pages, and other dynamically generated content can be compressed by using Gzip, adding other performance adjustment mechanisms and corresponding server-side cache rules can greatly improve the website performance.
First, describe the server environment: Windows2003 + IIS + PHP + ISAPI Rewrite. Check that the iis configuration content is correct, but the Gzip status is not enabled when querying the HTTP status, today, when I access a Discuz forum On the server, the bottom line is Gzip On. Is Gzip in PHP conflict with IIS? Run the test, open the PHP configuration file, disable the extension of php_zip.dll, and restart IIS.
After the preceding operations are completed, the Gzip status is enabled. In the past, there was no problem with the batch file opened by Gzip. The problem was that Gzip was also enabled in PHP, and there was a conflict when IIS was re-opened. It also illustrates another problem. The processing priority of PHP. ini is higher than that of Metabase. xml.
Article from: juyou