httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: httpd-2.0/docs/manual/howto ssi.html.en
Date Mon, 23 Jul 2001 15:50:47 GMT
slive       01/07/23 08:50:47

  Modified:    docs/manual upgrading.html
               docs/manual/mod mod_include.html
               docs/manual/howto ssi.html.en
  Some doc updates realted to ssi.
  1. Add info on how to activate ssi to upgrading.html.
  2. Remove mention of the ssi magic mime-types, since they no
  longer work.
  3. Place a warning on xbithack that it doesn't currently work,
  and reference the bug report.
  4. Add a warning about mod_include parsing non-html content.
  5. Misc little fixups.
  Revision  Changes    Path
  1.11      +20 -3     httpd-2.0/docs/manual/upgrading.html
  Index: upgrading.html
  RCS file: /home/cvs/httpd-2.0/docs/manual/upgrading.html,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -d -b -u -r1.10 -r1.11
  --- upgrading.html	2001/07/10 18:49:50	1.10
  +++ upgrading.html	2001/07/23 15:50:47	1.11
  @@ -24,9 +24,9 @@
   <LI>Apache now uses an <code>autoconf</code> and <code>libtool</code>
  -system for configuring the build processes.  Using this system
  -is similar to, but not the same as, using the APACI system in
  -Apache 1.3.  Further documentation to follow.</li>
  +system for <a href="install.html">configuring the build processes</a>.
  +Using this system is similar to, but not the same as, using the APACI
  +system in Apache 1.3.</li>
   <li>In addition to the usual selection of modules which you can choose
   to compile, Apache 2.0 has moved the main part of request processing
  @@ -36,12 +36,29 @@
   <H3>Run-Time Configuration Changes</H3>
   <li>Many directives that were in the core server in Apache 1.3
   are now in the MPMs.  If you wish the behavior of the server
   to be as similar as possible to the behavior of Apache 1.3,
   you should select the <a href="mod/prefork.html">prefork</a>
   MPM.  Other MPMs will have different directives to control process
   creation and request processing.</li>
  +<li>Server-Side Includes provided by <a
  +href="mod/mod_include.html">mod_include</a> are now implemented using
  +the new
  +<a href="filter.html">filter system</a> rather than as a handler.
  +This provides much more power and flexibility, but requires 
  +the use of the <a href="mod/core.html#setoutputfilter">SetOutputFilter</a>
  +to activate server-parsed content.  If you were using
  +<code>AddHandler server-parsed .shtml</code>, you can get
  +similar functionality using
  +&lt;FilesMatch "\.shtml(\..+)?$"&gt;<br>
  +&nbsp;&nbsp;SetOutputFilter INCLUDES<br>
   <li>The <code>CacheNegotiatedDocs</code> directive now takes
   the argument <code>on</code> or <code>off</code>.  Existing
  1.34      +19 -10    httpd-2.0/docs/manual/mod/mod_include.html
  Index: mod_include.html
  RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_include.html,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -d -b -u -r1.33 -r1.34
  --- mod_include.html	2001/05/07 00:42:21	1.33
  +++ mod_include.html	2001/07/23 15:50:47	1.34
  @@ -49,7 +49,7 @@
   <p>See also: <a href="core.html#options">Options</a>
  -and <a href="mod_mime.html#addhandler">AddHandler</a>.</p>
  +and <a href="core.html.html#SetOutputFilter">SetOutputFilter</a>.</p>
   <H2>Enabling Server-Side Includes</H2>
  @@ -68,6 +68,16 @@
  +<p>Be careful to properly scope the INCLUDES filter to process only
  +the correct files.  The filter is <strong>not</strong> restricted to
  +processing only HTML files.  So, for example, if the INCLUDES filter
  +is activated using a <code>&lt;Directory&gt;</code> section and that
  +directory includes GIF files, mod_include will process the GIF files.
  +This can have two adverse consequences: 1. there will be extra
  +overhead in serving these files, and 2. these files could become
  +corrupted if they happen to contain something that looks like an SSI
   <p>The following directive must be given for the directories containing
   the shtml files (typically in a <CODE>&lt;Directory&gt;</CODE> section,
   but this directive is also valid .htaccess files if <CODE>AllowOverride
  @@ -77,15 +87,8 @@
   Options +Includes
  -<p>Alternatively the <A HREF="#xbithack"><CODE>XBitHack</CODE></A>
  -directive can be used to parse normal (<CODE>text/html</CODE>) files,
  -based on file permissions.</p>
  -<p>For backwards compatibility, documents with mime type
  -<CODE>text/x-server-parsed-html</CODE> or
  -<CODE>text/x-server-parsed-html3</CODE> will also be parsed
  -(and the resulting output given the mime type <CODE>text/html</CODE>)
  -as will documents with the handler <code>server-parsed</code>.
  +<p>For more information, see our <a href="../howto/ssi.html">Tutorial
  +on Server Side Includes</a>.</p>
   <H2>Basic Elements</H2>
  @@ -441,6 +444,12 @@
   ><STRONG>Module:</STRONG></A> mod_include<P>
  +<p><strong>Warning:</strong> This directive is not yet working in
  +Apache 2.0.  The issue is being tracked in <a
   The XBitHack directives controls the parsing of ordinary html documents.
   This directive only affects files associated with the MIME type
  1.5       +1 -1      httpd-2.0/docs/manual/howto/ssi.html.en
  Index: ssi.html.en
  RCS file: /home/cvs/httpd-2.0/docs/manual/howto/ssi.html.en,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -d -b -u -r1.4 -r1.5
  --- ssi.html.en	2001/05/07 00:42:21	1.4
  +++ ssi.html.en	2001/07/23 15:50:47	1.5
  @@ -83,7 +83,7 @@
    <a href="../mod/core.html#options">Options</a><br>
   <a href="../mod/mod_include.html#xbithack">XBitHack</a><br>
   <a href="../mod/mod_mime.html#addtype">AddType</a><br>
  -<a href="../mod/mod_mime.html#addhandler">AddHandler</a><br>
  +<a href="../mod/core.html.html#setoutputfilter">SetOutputFilter</a><br>
   <a href=

View raw message