IIS 7 supports two different industry-standard compression schemes: The dynamicCompressionEnableCpuUsage and dynamicCompressionDisableCpuUsage attributes specify when IIS 7 will compress dynamic files based on CPU usage. Since dynamic content should change often, IIS 7 does not cache it.
However, dynamic content is typically content that is created by an application and therefore changes often, such as Active Server Pages (ASP) or ASP.NET content. This change is made because of the primary difference between static and dynamic content. Unlike static compression, IIS 7 performs dynamic compression each time a client requests the content, but the compressed version is not cached to disk. Image files such as *.jpg and *.png files are also static files, but typically they do not benefit from HTTP compression because these image files are already compressed. The size of these files can be reduced through compression, which reduces download times for client requests and reduces bandwidth on the server. You should use static compression with files that do not typically change, such as HTML files (*.html, *.htm), text files (*.txt), Microsoft Office documents (*.doc, *.xls, *.ppt), etc. The staticCompressionEnableCpuUsage and staticCompressionDisableCpuUsage attributes specify when IIS 7 will compress static files based on CPU usage. After IIS 7 has compressed a file, subsequent requests are given the compressed copy of the file from the cache directory. IIS 7 caches compressed static content in the path that is specified by the directory attribute, which increases compression performance by eliminating the need to recompress content that has already been compressed. There are two different types of compression that IIS 7 uses:
If a client is not capable of HTTP compression, it will not pass that header and IIS 7 will always return uncompressed content. An HTTP client must initiate communication for compressed content by sending the appropriate HTTP Accept-encoding header.
0 kommentar(er)
