<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://forums.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>Search results matching tag 'Content Type Header'</title><link>http://forums.iis.net/search/SearchResults.aspx?o=DateDescending&amp;tag=Content+Type+Header&amp;orTags=0</link><description>Search results matching tag 'Content Type Header'</description><dc:language>en-US</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>Bitrate throttling model should use Content Type Header</title><link>http://forums.iis.net/p/1150648/1874944.aspx#1874944</link><pubDate>Fri, 25 Jul 2008 02:30:29 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:1874944</guid><dc:creator>skumar2003</dc:creator><cs:applicationKey>iis7_-_media-41</cs:applicationKey><description>&lt;p&gt;All of the documentation on the bitrate throttling model uses the term MIME type. But in fact the module only responds when a url has a certain file extension (*.wmv, *.mov etc.)&lt;/p&gt;
&lt;p&gt;This design foraces us to have to implement our own handlers/module and the logic for throttling is media files are issued using dynamic urls such as a url to an aspx/ashx page.&lt;/p&gt;
&lt;p&gt;Now when responding with media files we do set the content type header. If the bitrate module actually looked at this header and applied its rules to these responses we wouldn&amp;#39;t have to do it ourselves.&lt;/p&gt;
&lt;p&gt;In the real world, I&amp;#39;ve never designed a system that produced a url such that links or users had direct access to media files. These file are frequently stored elsewhere and are not under the application root folder, and so throttling using a file extension in the url makes no sense in the real world.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;I&amp;#39;d love to see the bitrate throttling model respond to the content type header instead of the file extension in the url.&lt;/p&gt;</description></item></channel></rss>