A file’s MIME type specifies how a server or browser should interpret the file. For example, whether the file contains plain text, formatted HTML, an image, or a sound recording. In a Web server, MIME mappings specify how a static file should be interpreted by mapping file extensions to MIME types. MIME mappings affect only static files. Servlets and JSPs must be coded to specify a MIME type for their response.
For more information on MIME types, visit:
http://www.oac.uci.edu/indiv/ehood/MIME/MIME.html
EAServer includes preconfigured MIME mappings that you can customize using your Web application’s properties. Web application MIME mappings override EAServer’s preconfigured mappings.
MIME mappings include these properties:
Here is an example:
<mime-mapping> <extension>war</extension> <mime-type>application/zip.war</mime-type> </mime-mapping> <mime-mapping> <extension>jar</extension> <mime-type>application/zip.jar</mime-type> </mime-mapping>