try something like this:

<location name="/playlist" handler="playlist">

                    <filter-ref name="access-control-allow-origin-header"/>

                    <filter-ref name="content-mp4" predicate="path-suffix['.mp4']"/>

                    <filter-ref name="content-m3u8" predicate="path-suffix['.m3u8']"/>

                    <filter-ref name="content-jpg" predicate="path-suffix['.jpg'] or path-suffix['.jpeg']"/>

</location>

The issue is that the default servlet will set a content-type header, so your content-type will be overwritten. I will add a check for an existing content type header to the servlet to stop this happening [UNDERTOW-302] Default Servlet should check for existing content type header - JBoss Issue Tracker.

If you want to set a content type you can use the mime-mapping facility in web.xml:

<mime-mapping> 
  <extension>mp4</extension>
  <mime-type>video/mp4</mime-type> 
</mime-mapping>

Ah, sorry I did not notice that you were using the file handler. I have updated Undertow upstream so it will no longer set the content type.

I am using Wildfly 8.2 and have still the same problem. I would like to add a new content type "text/cache-manifest" for appcache files with ending ".manifest". InternetExplorer requires to get this content type, otherwise the app cache mechanism does not recognize the manifest and the mechanism will not work.

It seems that the Content-Type setting does not have any effect, I am always getting the Content-Type "application/octet-stream" for "*.manifest"-files.

As commented by Stuart in a post above, it seems the Content-Type will be still overridden.

When specifying any other header-name value (other than "Content-Type") then the response header setting below works, when setting "Content-Type" as header-name, the value is not set.

Is there a mistake in the setting below or any other possibility in wildfly to add a (new) content-type (other possibility then using web.xml, as we do not use it in an JEE environment)?

        <subsystem xmlns="urn:jboss:domain:undertow:1.2">

            <buffer-cache name="default"/>

            <server name="default-server">

                <ajp-listener name="ajp" socket-binding="ajp"/>

                <http-listener name="default" socket-binding="http"/>

                <host name="default-host" alias="localhost">

                    <location name="/" handler="welcome-content">

                        <filter-ref name="content-manifest" predicate="path-suffix['.manifest']"/>

                    </location>

                    <filter-ref name="server-header"/>

                    <filter-ref name="x-powered-by-header"/>

                    <filter-ref name="Cache-Control"/>

                    <filter-ref name="content-manifest" predicate="path-suffix['.manifest']"/>

                    <filter-ref name="myfilter"/>

                </host>

            </server>

            <servlet-container name="default">

                <jsp-config/>

                <websockets/>

            </servlet-container>

            <handlers>

                <file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>

            </handlers>

            <filters>

                <response-header name="content-manifest" header-name="Content-Type" header-value="text/cache-manifest"/>

                <response-header name="server-header" header-name="Server" header-value="WildFly/8"/>

                <response-header name="x-powered-by-header" header-name="X-Powered-By" header-value="Undertow/1"/>

                <response-header name="myfilter" header-name="agagag" header-value="agaga"/>

                <response-header name="Cache-Control" header-name="Cache-Control" header-value="no-cache, must-revalidate"/>

            </filters>

        </subsystem>

By the way the other filters "Cache-Control" and "myfilter" are working.

Bren, can you try this against the recently released WildFly 8.2.1.Final http://wildfly.org/downloads/ and see if it's working there?