Difference between revisions of "Adding MIME Types"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
When a Document or [[Static Resource]] is stored on the server, the appropriate {{^MIME}} type must be specified when the file is sent to the user's browser, so the browser knows what to do with that file. | When a Document or [[Static Resource]] is stored on the server, the appropriate {{^MIME}} type must be specified when the file is sent to the user's browser, so the browser knows what to do with that file. Normally, that process happens automatically: The most common file extensions are already recognized by the platform, and the file extension determines which MIME type is specified. | ||
When a file has an extension that the platform does not recognize, however, the file may be mishandled when it reaches the browser. That problem can be fixed by adding a line to the <tt>Apache/conf/httpd.conf</tt> configuration file: | |||
That problem can be fixed by adding a line to the <tt>Apache/conf/httpd.conf</tt> configuration file: | |||
:{| | :{| | ||
<pre>AddType MIME_TYPE FILE_EXTENSION</pre> | <pre>AddType MIME_TYPE FILE_EXTENSION</pre> | ||
Revision as of 20:34, 2 October 2013
When a Document or Static Resource is stored on the server, the appropriate MIME type must be specified when the file is sent to the user's browser, so the browser knows what to do with that file. Normally, that process happens automatically: The most common file extensions are already recognized by the platform, and the file extension determines which MIME type is specified.
When a file has an extension that the platform does not recognize, however, the file may be mishandled when it reaches the browser. That problem can be fixed by adding a line to the Apache/conf/httpd.conf configuration file:
AddType MIME_TYPE FILE_EXTENSION
For example, to configure an HTML5 cache file with extension .appcache, add the following:
AddType text/cache-manifest .appcache