The Windows Internet Information Services (IIS) Manager performs dynamic compression each time a client requests the content, but the compressed version is not cached to disk. Dynamic content is typically created by an application and changes often, such as Active Server Pages (ASP) or ASP.NET content. Because of frequent changes, the IIS does not cache the content.
Enable dynamic compression for a site or application
-
In Control Panel, click Programs and Features, and then click Turn Windows features on or off.
-
Expand Internet Information Services > World Wide Web Services >Performance Features, and then select Dynamic Content Compression and/or Static Content Compression. Click OK.
-
Open Internet Information Services (IIS) Manager.
-
In the Connections pane, go to the connection, site, application, or directory to enable compression.
-
In the Home pane, double-click Compression.
-
In the Compression pane, check Enable dynamic content compression.
-
Click Apply in the Actions pane.
-
Open the IIS Configuration Editor and perform the following in the specified section:
Section system.webServer/httpCompression:
-
Increase the maxDiskSpaceUsage as the default value of 100 MB is too small. We recommend 10 GB or more, if possible. If you continue to use the default (100 MB), the server must constantly recompress files.
-
Edit dynamicTypes, and then add application/octet-stream and application/wasm.
-
Change sendCacheHeaders from False to True.
-
Set the same configuration directly in the root web.config:
When Dynamic compression is enabled, you can see Content-Encoding: gzip in the Response Headers whenever your application requests data on the dynamic compression-enabled server.
-
The transferred data is also reduced for dynamic compression.