Skip to main content
added 195 characters in body
Source Link
Brian
  • 313
  • 1
  • 4
  • 15

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses dynamic compression on that request. This can be resolved by setting the serverRuntime element's frequentHitTHreshold attribute to 1.

This is discussed in detail here. This setting is probably only worth changing if serving a CDN.

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses dynamic compression on that request. This can be resolved by setting the serverRuntime element's frequentHitTHreshold attribute to 1.

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses dynamic compression on that request. This can be resolved by setting the serverRuntime element's frequentHitTHreshold attribute to 1.

This is discussed in detail here. This setting is probably only worth changing if serving a CDN.

added 103 characters in body
Source Link
Brian
  • 313
  • 1
  • 4
  • 15

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses weakerdynamic compression on that request. This can be resolved by setting the serverRuntime element's frequentHitTHreshold attribute to 1.

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses weaker compression on that request.

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses dynamic compression on that request. This can be resolved by setting the serverRuntime element's frequentHitTHreshold attribute to 1.

Source Link
Brian
  • 313
  • 1
  • 4
  • 15

Apparently, on the first request for a static file, IIS does not have a compressed copy of the file in it's compressed file cache, so it uses weaker compression on that request.