2

I've managed to set up compression for a custom mime type on IIS 7.5 with no problem. Add the mime type to IIS then add it to the httpCompression element in applicationHost.config. But when I do the same thing on IIS 7, the particular mime type is never compressed. This isn't a problem with compression in general since other mime types are compressed correctly. As far as I can tell, IIS 7 and IIS7.5 are configured in exactly the same way. Does IIS7 behave differently and do I need to do something else to get it working?

I've setup failed request tracing and get a NO_MATCHING_CONTENT_TYPE error during compression but I can't figure out what else I need to do to tell IIS about my mime type

1
  • Post the relevant portions of applicationHost.config. What specific MIME Type doesn't compress? Feb 12, 2012 at 0:19

1 Answer 1

0

Suggestion! Either use an XML-capable comparison tool like BeyondCompare, or like Web Deployment Tool (-verb:sync -whatif) to compare configurations, particularly at the applicationhost.config level.

2
  • Thanks, there are some differences between the applicationHost.config files but nothing that looks like it would explain the difference
    – Doogal
    Apr 11, 2011 at 16:24
  • It'd help to have comparative FREB logs. Otherwise - does the Windows level know about the file type on one, and not the other? (is the Mime type registered in the registry on one of the boxes?)
    – TristanK
    Apr 12, 2011 at 7:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .