MIME Type Support (commons.mime)
Support for MIME type mappings is generally a problematic issue. On the one hand applications have to take care to stay up to date with their mappings on the other hands in web applications it is tedious to maintain the mappings. Apache Sling takes a very user and deployment friendly approadch to this problem which is described in detail on this page.
Servlet API Support
The Servlet API specification provides a limited support for MIME type mappings :
- Mappings may be defined in the
mime-mappingelements of the the web application descriptor
web.xml. Managing these mappings is presumably tedious. So servlet containers may provide reasonable defaults (or not).
ServletContext.getMimeType(String)returns a MIME type for a given file name based on the extension of the filename. The mapping returned is based on the servlet container configuration as well as the web application descriptor's
Enter Sling: The MimeTypeService
Already at the start of the Sling project we realized, that just basing the MIME type mapping decisions on the servlet container will not yield acceptable results. For this reason the Apache Sling projects provides a spezialized and configurable service supporting such mappings: The
This service provides access to registered MIME types and their mappings with two methods:
getExtension(String)-- given a MIME type this methods returns a primary extension. For example for the type
text/plainthis method will return
getMimeType(String)-- given a file name or just the extension) returns the mapped MIME type. For example for the filename
sample.html(or just the extension
html) this method will return
Two more method allow to programmatically add MIME type mappings:
registerMimeType(InputStream)registers additional mappings from the given input stream which is expected to be formated in traditional
mime.typesfile format (see below).
registerMimeType(String, String...)registers a single mapping for the give MIME type and the respective extensions.
MimeTypeService provided by Apache Sling, there is actually more:
getResponseContentType()method, which returns the preferred Content-Type for the response based on the requests extension. This method is implemented by Apache Sling using the
MimeTypeService. So servlets and scripts may just call this method to set the content type of the response to the desired value.
- Each Servlet (and JSP scripts) is initialized by Apache Sling with a
ServletContextinstance whose implementation of the
getMimeType(String)effectively calls the
- The Scripting support infrastructure of Sling sets the response content type on behalf of the script to the default value as returned by the
SlingHttpServletRequest.getResponseContentType()method. At the same time the response character set is also set to
UTF-8for text content types.
Configuring MIME Type Mappings
The implementation of the
MimeTypeService in the Apache Sling MIME type mapping support (
org.apache.sling.commons.mime) bundle supports a numnber of ways to configure and extend the set of MIME type mappings:
- Default configuration. The default configuration is based on the
mime.typesfile maintained by Roy Fielding for the Apache httpd project and some extensions by Apache Sling.
- Bundle provided mappings. Bundles registered in the OSGi framework may contain MIME type mappings files
META-INF/mime.typeswhich are loaded automatically by the Apache Sling MIME type mapping support bundle.
- Configuration. Mappings may be supplied by configuration of the
MimeTypeServiceimplementation as the multi-value string property
mime.types. Each value of the property corresponds to a line in a MIME type configuration file (see below for the format).
- Registered Mappings. Mappings may be registered with the
MimeTypeProvider. Additional mappings may be provided by service implementing the
MimeTypeServiceimplementation will call these services in turn until a service returns a mapping provided there is no static configuration to responde to the mapping request.
Please note, that existing mappings cannot be overwritten later. Thus mappings have an inherent priority:
- Mappings provided by the Apache httpd project's
- Extensions by the Apache Sling MIME type mapping support bundle
- Bundles providing a
META-INF/mime.typesfile in the order of their bundle-id (or startup order if started after the MIME type mapping support bundle)
- OSGi Configuration. Note that bundles started after the MIME type mapping support bundle may not overwrite mappings provided by the OSGi configuration. This may sounds like a problem, but in reality this should genrally not matter
- Mappings registered calling the
- Mappings provided by
MIME Type Mapping File Format
The file format for MIME type mapping files is rather simple:
- The files are assumed to be encoded with the ISO-8859-1 (aka Latin 1) character encoding
- The files consist of lines defining mappings where each line is terminated with either or both of a carriage return (CR, 0x0c) and line feed character (LF, 0x0a). There is no line continuation support *-la shell scripts or Java properties files.
- Empty lines and lines starting with a hash sign (
#) are ignored
- Data lines consist of space (any whitespace matching the
\sregular expression) separated values. The first value is the MIME type name and the remaining values defining mappings to file name extensions. The first listed file name extension is considered the default mapping and is returned by the
MimeTypeService.getExtension(String)method. Entry lines consisting of just a mime type but no extensions are also (currently) ignored.
THe data line format described here also applies to configuration provided by the values of the
mime.types property of the MIME type service configuration. The file format description applies to all
META-INF/mime.types files provided by the bundles as well as input streams supplied to the
Web Console Plugin
The Apache Sling MIME type mapping support bundle implements a plugin for the Apache Felix Web Console which may be consulted to investigate the current contents of the MIME type mapping tables.