httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Sutton <>
Subject cvs commit: apache/htdocs/manual/mod mod_mime.html
Date Sat, 07 Jun 1997 12:53:03 GMT
pcs         97/06/07 05:53:02

  Modified:    htdocs/manual/mod  mod_mime.html
  Update the summary part of mod_mime documentation to:
    - not state that extensions must be given in a particular order
    - mention assigning of handlers and use of info in content-negotiation
    - mention effect of 'unknown' extensions
  Revision  Changes    Path
  1.13      +37 -15    apache/htdocs/manual/mod/mod_mime.html
  Index: mod_mime.html
  RCS file: /export/home/cvs/apache/htdocs/manual/mod/mod_mime.html,v
  retrieving revision 1.12
  retrieving revision 1.13
  diff -C3 -r1.12 -r1.13
  *** mod_mime.html	1997/06/07 12:27:50	1.12
  --- mod_mime.html	1997/06/07 12:53:01	1.13
  *** 20,41 ****
    from the filename.
  - This module is used to determine the mime types of documents. Some mime
  - types indicate special processing to be performed by the server, otherwise
  - the type is returned to the client so that the browser can deal with
  - the document appropriately.<p>
  - The filename of a document is treated as being composed of a basename followed
  - by some extensions, in the following order:
  - <blockquote><em>base.type.language.enc</em></blockquote>
  - The <em>type</em> extension sets the type of the document; types are defined
  - in the <A HREF="#typesconfig">TypesConfig</A> file and by the
  - <A HREF="#addtype">AddType</A> directive. The <em>language</em>
  - sets the language of the document, as defined by the
  - <A HREF="#addlanguage">AddLanguage</A> directive. Finally, the
  - <em>enc</em> directive sets the encoding of the document, as defined by
  - the <A HREF="#addencoding">AddEncoding</A> directive.
    <h2> Directives</h2>
  --- 20,63 ----
    from the filename.
  + This module is used to determine various bits of "meta information"
  + about documents. This information relates to the content of the
  + document and is returned to the browser or used in content-negotiation
  + within the server. In addition, a "handler" can be set for a document,
  + which determines how the document will be processed within the server.
  + <P>
  + The directives <A HREF="#addencoding">AddEncoding</A>, <A
  + HREF="#addhandler">AddHandler</A>, <A
  + HREF="#addlanguage">AddLanguage</A> and <A HREF="#addtype">AddType</A>
  + are all used to map file extensions onto the meta-information for that
  + file.  Respectively they set the content-encoding, handler,
  + content-language and mime-type (content-type) of documents.  The
  + directive <A HREF="#typesconfig">TypesConfig</A> is used to specify a
  + file which also maps extensions onto mime types. The directives <A
  + HREF="#forcetype">ForceType</A> and <A
  + HREF="#sethandler">SetHandler</A> are used to associated all the files
  + in a given location (e.g. a particular directory) onto a particular
  + mime type or handler.
  + <P>
  + Files can have more than one extension, and the order of the
  + extensions is normally irrelevant. For example, if the file
  + <CODE></CODE> maps onto content type text/html and
  + language French then the file <CODE></CODE> will map
  + onto exactly the same information. The only exception to this is if an
  + extension is given which Apache does not know how to handle. In this
  + case it will "forget" about any information it obtained from
  + extensions to the left of the unknown extension. So, for example, if
  + the extensions fr and html are mapped to the appropriate language and
  + type but extension xxx is not assigned to anything, then the file
  + <CODE></CODE> will be associated with content-type
  + text/html but <i>no</i> language.
  + <P>
    <h2> Directives</h2>

View raw message