MIME Content-Type

   HTTP/1.0 uses an IANA standard "Mime Content-type" classification for
   the files served. Examples of such types are "text/plain",
   "image/gif", etc. Starting with version 1.0 the _gn_ server needs to
   know this type to transmit to the client. This is normally
   accomplished automatically using the file gn_mime.types which can be
   edited by server maintainer. Information in this file enables mkcache
   program to translate the gopher Type= field and the suffix from the
   file name into a standard type. For example, the line

     I<tab>gif<tab>image/gif

   
   
   in gn_mime.types means that menu items with Type=I and a file name
   like picture.gif should be given the "image/gif" type. This assignment
   can be overridden on a per file basis by adding a line to the menu
   file. For example, a menu item like

        Name=An html file
        Path=0/dir/filename
        ContentType=text/html
        Type=0

   
   
   will be given the Content-type "text/html" even though the file name
   does not end with the suffix ".html" (had the file name been
   filename.html it would not have been necessary to add the ContentType=
   line. There is a similar "ContentEncoding" field to indicate that a
   file is compressed. For example, the entry

        Name=A compressed Postscript file
        Path=9/dir/filename.ps.gz
        ContentType=application/postscript
        ContentEncoding=x-gzip
        Type=9

   
   
   would be appropriate for a compressed Postscript file. A content
   encoding should not be used with files of type 0Z or 9Z (see the
   section on compressed files) because these are decompressed on the
   server so the client should not be told they are compressed. If
   standard suffixes (as described in the gn_mime.types file) are used
   _gn_ can infer the correct values of ContentType and ContentEncoding,
   so these need not be in the menu file. These attributes are only used
   with clients supporting the HTTP/1.0 protocol. Gopher0 clients and
   HTTP/0.9 protocol clients are not capable of using this information.
   
   If the file gn_mime.types is not present mkcache will issue a warning
   but use internal default values. The file exists so that you can add
   to it if you wish to add new kinds of documents to your server. The
   format of the file is explained in the file. The default version of
   the file is in mkcache/gn_mime.types. The internal defaults are the
   same as what is currently in this file.
   
.