httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_include.html
Date Thu, 05 Feb 1998 09:58:41 GMT
martin      98/02/05 01:58:40

  Modified:    htdocs/manual/misc FAQ.html
               htdocs/manual/mod mod_include.html
  Added:       htdocs/manual/images custom_errordocs.gif
               htdocs/manual/misc custom_errordocs.html
  Add a document describing a solution which uses XSSI and negotiation
  to custom-tailor the apache ErrorDocuments to taste, adding the
  advantage of returning internationalized versions of the error
  messages depending on the client's language preferences.
  Revision  Changes    Path
  1.1                  apache-1.3/htdocs/manual/images/custom_errordocs.gif
  Index: custom_errordocs.gif
  J:'i8 wxDEAObŨ+JъX'p)3*Bka&~pF76…"qFˑe#q̤&-a:«xL`8HAVi4#
  i?fQiL*YZf|e kMx%[qk,wiKJ(Cf.UIGiZ4sJJ"2461..6nN];SzS@9Ij<A#9NjJd5)I6=7m:Pc2i!$zӉ^*!IJFSGQQ.PS8GV
<*ֲ +Zֶ~Bn\txͫ^׾

  EaOcL<]// XwkJz
  Uxa[W̨Xx؏XSwxi\y'9YySR]8	^壐x(*,ْ.`"IH=
  ٙkY	m;ꇌX;
  Zx6psZg*aꥒhڝWZcNIM꥜OZ*jlA(zhuzhd]uGlJڣp%
  <<dG]H "<$\&L<M	^.|﫽,4\6|8:YW@B<D\F|H|X
8zӉYIgi}zp\Uo#%2Mfk*ݜQ8RtkYԘ{\\ӳjӃpʪrl0
MzMym[{׻bȔlЃ˻LBMŭ
  l]W\x3m/I֨}؂=جn^|/Pl
ј,'½א)ڡMׯ-\]ܾ
  :0 *@jZ
  ^$$cI8ֹIVks>25!6E+`#XJLC@aK璎
sḇzN 0EAhy
  6sGp#؀RH_EyQR`18.C5;R$;^p$U'@7zVpA;Sn%Z?/>o
  P0lG4~40,u۠fumX JL}
ff\e4PaQ@t$VGt-˛$A'}´u@	\0{~I0R
  82=Gv$eNw'Yi X@&8N
  f魧\:Cfkyq!We nBdZ#dZՙpl)\HyL:ׄS B~rc#RM0yG{&mT
MU$IxB;P-IJ4Bd?O[j+Df8L*uźt٪Q8̾&R)WeLPCM+uNNܶ>;W{"t\Xmc

  3[J#6$[ah}#}%	))-0 lU+$=ҤWbJh{.
  > ^m180r2c(9-/Cx$"P0Rޅ?:L m->0#{%L'jٓFN\@>Kn?02S#P=
Q[	~$D
UQ"[|	%%䉠dFRF2e+DaVG\%R\uF2%6`_sSWTI7
  */,҆CLV9ƖGA:AtP"p`	NH(l`j`>,(R
  FqjD0I v{ϒ%؏w]n^@-EIŻؗH"/:	ʶ6=Vd1$'f^h>Aopߑibؗy4Îw6
  sL`#3L2l ,ъn&!).R0A.e
  w煮vɫz{IP_9!8K^ĝ݁zpr֯ʷ+a׾0x^6{9Ķ80~FAk]حZJlc|aU%q?\
WT}d"p̒οE}T}fu>.+2]dx0WBgA_nLir5j>wv2}O3ٱ\}1|k:͕jWznto%c]kra=PƥkcXUž~UmVTW{SV'v[Wm;N,QmbAraZi#6vhe͎R,C5e0'>Ye2pCNX\@DeZ*.//!)Rc7m@{fեAOҗΗb6ӧN)
  ~~Ȁi Nc=

  +{겣7*oVn[g:Vl{٪0GjܸȋsUGmvfSIehf;ش[eC˚JxK',|1۷"k2;{K%ŔwY{XkNEXfj!p˔Ka!&FkvYg9DkHJkʋ7k0뼐˼wK![6^[)b㛻t+8ok|O?`/[Yƺ1LjuuVF{lۼ۸/ۮ{k<{C6+`x2g(;ڧ4J)L替~¬utٹ|feSܺP/Dwk5k%6{gDGLn3i-'1iy2iŸȌ,m2M;|ŎxOrzk۷{"|*ŀ;˷h<k|Xǘ7uGxjh{ىyűM܁Hmx陕}ͫi
  zO';<7{x*y~2k	5Qc1[!Â%7Đ?hrY
:ȍ5}WC=ݝ<Gm}m2 |=	nÀG--% w=۝i̊}8X^~
  >^~ >"^$~&^v}w yz6.
?]{`ťn|Iqݡ}G$PLW='HܛKȯy&MnD%V%We8xNWR(qj`;j)}f^D묎󆎽]e೮V9n`VCr>j^@]\eXhlniԶhZoɨugҎѐ]WckMƹ;bkv`Q+gnƨ9{,Qs
  =	7ܹtmjG^ŲubÆVXLu;(*
  FB*ƑW.aAgbt̂' `Qve`S/dq1De0/Lу$x"BI$]
  8WX'S2/fދoIKjPD aC+rt 
  4Gpbw #lD.ntcJXVClOފᜤ@*2(|p0_,:n<at)*`
Gy~z'z\{|t>'.7u!wxMWzwzhxxW|(7'yGxr	xn#|zu$Xur0S{RvPr+vg}ta6uDcce'.LI(BU(j'p`_X(ciN((PhjdkH?$l(sindgt{HefД|(HdZ*.ԅ@?F舲Hanlx։au灔^GnHv˷,Ln_д<y(@A¸qvGx~挛PHxohfȅ76(H#X
Vx8Ϩ	HX8`~
  W>tȏ_wEwV	xN'{2(,(y,׀;i'pg(u-"q鑛rƁ1	uǒ/1x>t6y3HM
  "󰋘!v|v9ұKOQ%GGJ	H
  zk|ˉalΆLCle;Ql̅<h|xڂ:>O8ɶ
ґ	ҳkdcд5m79;=?

  Fdf	XR
  1.105     +17 -1     apache-1.3/htdocs/manual/misc/FAQ.html
  Index: FAQ.html
  RCS file: /home/cvs/apache-1.3/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.104
  retrieving revision 1.105
  diff -u -u -r1.104 -r1.105
  --- FAQ.html	1998/01/26 16:53:48	1.104
  +++ FAQ.html	1998/02/05 09:58:38	1.105
  @@ -15,7 +15,7 @@
     <!--#include virtual="header.html" -->
     <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
  -  $Revision: 1.104 $ ($Date: 1998/01/26 16:53:48 $)
  +  $Revision: 1.105 $ ($Date: 1998/02/05 09:58:38 $)
     The latest version of this FAQ is always available from the main
  @@ -142,6 +142,9 @@
      <LI><A HREF="#errordoc401">Why doesn't my <CODE>ErrorDocument
       401</CODE> work?</A>
  +   <LI><A HREF="#errordocssi">How can I use <CODE>ErrorDocument</CODE>
  +   and SSI to simplify customized error messages?</A>
  +   </LI>
      <LI><A HREF="#setgid">Why do I get &quot;<SAMP>setgid: Invalid
       argument</SAMP>&quot; at startup?</A>
  @@ -1082,6 +1085,19 @@
     documentation for details.  This was incorrectly documented in the past.
  +  </P>
  +  <HR>
  + </LI>
  + <LI><A NAME="errordocssi">
  +      <STRONG>How can I use <CODE>ErrorDocument</CODE>
  +   and SSI to simplify customized error messages?</STRONG>
  +     </A>
  +  <P>
  +  Have a look at <A HREF="custom_errordocs.html">this document</A>.
  +  It shows in example form how you can a combination of XSSI and
  +  negotiation to tailor a set of <CODE>ErrorDocument</CODE>s to your
  +  personal taste, and returning different internationalized error
  +  responses based on the client's native language.
  1.1                  apache-1.3/htdocs/manual/misc/custom_errordocs.html
  Index: custom_errordocs.html
  <title>International Customized Server Error Messages</title>
  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
   <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]">
  <H1 ALIGN="CENTER">Using XSSI and <SAMP>ErrorDocument</SAMP> to configure
  customized international server error responses</H1>
   <LI><A HREF="#intro">Introduction</A>
   <LI><A HREF="#createdir">Creating an ErrorDocument directory</A>
   <LI><A HREF="#docnames">Naming the individual error document files</A>
   <LI><A HREF="#headfoot">The common header and footer files</A>
   <LI><A HREF="#createdocs">Creating ErrorDocuments in different languages</A>
   <LI><A HREF="#fallback">The fallback language</A>
   <LI><A HREF="#listings">HTML listing of the discussed example</A>
  <A NAME="intro"><H2>Introduction</H2></A>
  This document describes an easy way to provide your apache WWW server
  with a set of customized error messages which take advantage of
  <A HREF="../content-negotiation.html">Content Negotiation</A>
  and <A HREF="../mod/mod_include.html">eXtended Server Side Includes (XSSI)</A>
  to return error messages generated by the server in the client's
  native language.
  By using XSSI, all <A HREF="../mod/core.html#errordocument">customized messages</A>
  can share a homogenous and consistent style and layout, and maintenance work
  (changing images, changing links) is kept to a minimum because all layout
  information can be kept in a single file.<BR>
  Error documents can be shared across different servers, or even hosts,
  because all varying information is inserted at the time the error document
  is returned on behalf of a failed request.
  Content Negotiation then selects the appropriate language version of a
  particular error message text, honoring the language preferences passed
  in the client's request. (Users usually select their favorite languages
  in the preferences options menu of today's browsers). When an error
  document in the client's primary language version is unavailable, the 
  secondary languages are tried or a default (fallback) version is used.
  You have full flexibility in designing your error documents to
  your personal taste (or your company's conventions). For demonstration
  purposes, we present a simple generic error document scheme.
  For this hypothetic server, we assume that all error messages...
  <LI>possibly are served by different virtual hosts (different host name,
      different IP address, or different port) on the server machine,
  <LI>show a predefined company logo in the right top of the message
      (selectable by virtual host),
  <LI>print the error title first, followed by an explanatory text and
      (depending on the error context) help on how to resolve the error,
  <LI>have some kind of standardized background image,
  <LI>display an apache logo and a feedback email address at the bottom
      of the error message.
  An example of a "document not found" message for a german client might
  look like this:<BR>
  <IMG SRC="../images/custom_errordocs.gif"><BR>
  All links in the document as well as links to the server's administrator
  mail address, and even the name and port of the serving virtual host
  are inserted in the error document at "run-time", i.e., when the error
  actually occurs.
  <A NAME="createdir"><H2>Creating an ErrorDocument directory</H2></A>
  For this concept to work as easily as possible, we must take advantage
  of as much server support as we can get:
   <LI>By defining the <A HREF="../mod/core.html#options">MultiViews option</A>,
       we enable the language selection of the most appropriate language
       alternative (content negotiation). 
   <LI>By setting the <A HREF="../mod/mod_negotiation.html#languagepriority">LanguagePriority</A>

       directive we define a set of default fallback languages in the situation
       where the client's browser did not express any preference at all.
   <LI>By enabling <A HREF="../mod/mod_include.html">Server Side Includes</A>
       (and disallowing execution of cgi scripts for security reasons),
       we allow the server to include building blocks of the error message,
       and to substitute the value of certain environment variables into the
       generated document (dynamic HTML) or even to conditionally include
       or omit parts of the text.
   <LI>The <A HREF="../mod/mod_mime.html#addhandler">AddHandler</A> and
       <A HREF="../mod/mod_mime.html#addtype">AddType</A> directives are useful
       for automatically XSSI-expanding all files with a <SAMP>.shtml</SAMP>
       suffix to <em>text/html</em>.
   <LI>By using the <A HREF="../mod/mod_alias.html#alias">Alias</A> directive,
       we keep the error document directory outside of the document tree
       because it can be regarded more as a server part than part of
       the document tree.
   <LI>The <A HREF="../mod/core.html#directory">&lt;Directory&gt;</A>-Block
       restricts these "special" settings to the error document directory
       and avoids an impact on any of the settings for the regular document tree.
   <LI>For each of the error codes to be handled (see RFC2068 for an exact
       description of each error code, or look at <CODE>src/main/http_protocol.c</CODE>
       if you wish to see apache's standard messages), an
       <A HREF="../mod/core.html#errordocument">ErrorDocument</A>
       in the aliased <SAMP>/errordocs</SAMP> directory is defined.
       Note that we only define the basename of the document here
       because the MultiViews option will select the best candidate
       based on the language suffixes and the client's preferences.
       Any error situation with an error code <em>not</em> handled by a
       custom document will be dealt with by the server in the standard way
       (i.e., a plain error message in english).
   <LI>Finally, the <A HREF="../mod/core.html#allowoverride">AllowOverride</A>
       directive tells apache that it is not necessary to look for 
       a .htaccess file in the /errordocs directory: a minor speed 
  The resulting <SAMP>httpd.conf</SAMP> configuration would the look
  similar to this: <small>(Note that you can defrine your own error
  messages using this method for only part of the document tree,
  e.g., a /~user/ subtree. In this case, the configuration could as well
  be put into the .htaccess file at the root of the subtree. In this case,
  the &lt;Directory&gt; and &lt;/Directory&gt; directives -but not
  the contained directives- must be omitted.)</small>
    LanguagePriority en fr de 
    Alias  /errordocs  /usr/local/apache/errordocs
    &lt;Directory /usr/local/apache/errordocs&gt;
     AllowOverride none
     Options MultiViews IncludesNoExec FollowSymLinks
     AddType text/html .shtml
     AddHandler server-parsed .shtml
    #    "400 Bad Request",
    ErrorDocument  400  /errordocs/400
    #    "401 Authorization Required",
    ErrorDocument  401  /errordocs/401
    #    "403 Forbidden",
    ErrorDocument  403  /errordocs/403
    #    "404 Not Found",
    ErrorDocument  404  /errordocs/404
    #    "500 Internal Server Error",
    ErrorDocument  500  /errordocs/500
  The directory for the error messages (here:
  <SAMP>/usr/local/apache/errordocs/</SAMP>) must then be created with the
  appropriate permissions (readable and executable by the server uid or gid, 
  only writable for the administrator).
  <A NAME="docnames"><H3>Naming the individual error document files</H3></A>
  By defining the <SAMP>MultiViews</SAMP> option, the server was told to
  automatically scan the directory for matching variants (looking at language
  and content type suffixes) when a requested document was not found.
  In the configuration, we defined the names for the error documents to be
  just their error number (without any suffix).
  The names of the individual error documents are now determined like this
  (I'm using 403 as an example, think of it as a placeholder for any of
  the configured error documents):
   <LI>No file errordocs/403 should exist. Otherwise, it would be found and
       served (with the DefaultType, usually text/plain), all negotiation
       would be bypassed.
   <LI>For each language for which we have a translation (note that this need not
       be the same set of languages for each error code - you can get by
       with a single language version until you actually <em>have</em>
       translated versions), a document
       <SAMP>errordocs/403.shtml.<em>lang</em></SAMP> is created and
       filled with the error text in that language (<A HREF="#createdocs">see
   <LI>One fallback document called <SAMP>errordocs/403.shtml</SAMP> is
       created, usually by creating a symlink to the default language
       variant (<A HREF="#fallback">see below</A>).
  <A NAME="headfoot"><H3>The common header and footer files</H3></A>
  By putting as much layout information in two special "include files", 
  the error documents can be reduced to a bare minimum.
  One of these layout files defines the HTML document header
  and a configurable list of paths to the icons to be shown in the resulting
  error document. These paths are exported as a set of XSSI environment
  variables and are later evaluated by the "footer" special file.
  The title of the current error (which is
  put into the TITLE tag and an H1 header) is simply passed in from the main
  error document in a variable called <CODE>title</CODE>.<BR>
  <STRONG>By changing this file, the layout of all generated error
  messages can be changed in a second.</STRONG>
  (By exploiting the features of XSSI, you can easily define different
  layouts based on the current virtual host, or even based on the
  client's domain name).
  The second layout file describes the footer to be displayed at the bottom
  of every error message. In this example, it shows an apache logo, the current
  server time, the server version string and adds a mail reference to the
  site's webmaster.
  For simplicity, the header file is simply called <CODE>head.shtml</CODE>
  because it contains server-parsed content but no language specific
  information. The footer file exists once for each language translation,
  plus a symlink for the default language.<P>
  <STRONG>Example:</STRONG> for english, french and german versions (default english)<BR>
  <CODE>foot.shtml</CODE> symlink to <CODE>foot.shtml.en</CODE><P>
  Both files are then simply included into the error document by using the
  directives <CODE>&lt;!--#include virtual="head" --&gt;</CODE>
  and        <CODE>&lt;!--#include virtual="foot" --&gt;</CODE>
  respectively: the rest of the magic occurs in mod_negotiation and
  in mod_include.
  See <A HREF="#listings">the listings below</A> to see an actual HTML
  implementation of the discussed example.
  <A NAME="createdocs"><H3>Creating ErrorDocuments in different languages</H3></A>
  After all this preparation work, little remains to be said about the
  actual documents. They all share a simple common structure:
  &lt;!--#set var=&quot;title&quot; value=&quot;<EM>error description
title</EM>&quot; --&gt;
  &lt;!--#include virtual=&quot;head&quot; --&gt;
     <EM>explanatory error text</EM>
  &lt;!--#include virtual=&quot;foot&quot; --&gt;
  In the <A HREF="#listings">listings section</A>, you can see an example
  of a [400 Bad Request] error document. Documents as simple as that
  certainly cause no problems to translate or expand.
  <A NAME="fallback"><H3>The fallback language</H3></A>
  Do we need a special handling for languages other than those we have
  translations for? We did set the LanguagePriority, didn't we?!
  Well, the LanguagePriority directive is for the case where the client does
  not express any language priority at all. But what
  happens in the situation where the client wants one
  of the languages we do not have, and none of those we do have?
  Without doing anything, the Apache server will usually return a
  [406 no acceptable variant] error, listing the choices from which the client
  may select. But we're in an error message already, and important error
  information might get lost when the client had to choose a language
  representation first.
  So, in this situation it appears to be easier to define a fallback language
  (by copying or linking, e.g., the english version to a language-less version).
  Because the negotiation algorithm prefers "more specialized" variants over
  "more generic" variants, these generic alternatives will only be chosen
  when the normal negotiation did not succeed.
  A simple shell script to do it (execute within the errordocs/ dir):
    for f in *.shtml.en
       ln -s $f `basename $f .en`
  <A NAME="listings"><H2>HTML listing of the discussed example</H2></A>
  So, to summarize our example, here's the complete listing of the
  <SAMP>400.shtml.en</SAMP> document. You will notice that it contains
  almost nothing but the error text (with conditional additions).
  Starting with this example, you will find it easy to add more error
  documents, or to translate the error documents to different languages.
  &lt;!--#set var=&quot;title&quot; value=&quot;Bad Request&quot;
  --&gt;&lt;!--#include virtual=&quot;head&quot; --&gt;&lt;P&gt;
     Your browser sent a request that this server could not understand:
       &lt;STRONG&gt;&lt;!--#echo var=&quot;REQUEST_URI&quot; --&gt;&lt;/STRONG&gt;
     The request could not be understood by the server due to malformed
     syntax. The client should not repeat the request without
     &lt;!--#if expr=&quot;\&quot;$HTTP_REFERER\&quot; != \&quot;\&quot;&quot;
      Please inform the owner of
      &lt;A HREF=&quot;&lt;!--#echo var=&quot;HTTP_REFERER&quot; --&gt;&quot;&gt;the
referring page&lt;/A&gt; about 
      the malformed link.
     &lt;!--#else --&gt;
      Please check your request for typing errors and retry.
     &lt;!--#endif --&gt;
  &lt;!--#include virtual=&quot;foot&quot; --&gt;
  Here is the complete <SAMP>head.shtml</SAMP> file (the funny line
  breaks avoid empty lines in the document after XSSI processing). Note the 
  configuration section at top. That's where you configure the images and logos
  as well as the apache documentation directory. Look how this file displays
  two different logos depending on the content of the virtual host name
  ($SERVER_NAME), and that an animated apache logo is shown if the browser
  appears to support it (the latter requires server configuration lines
  of the form <BR><CODE>BrowserMatch "^Mozilla/[2-4]" anigif</CODE><BR>
  for browser types which support animated GIFs).
  &lt;!--#if expr=&quot;\&quot;$SERVER_NAME\&quot; = /.*\.mycompany\.com/&quot;

  --&gt;&lt;!--#set var=&quot;IMG_CorpLogo&quot;

  --&gt;&lt;!--#set var=&quot;ALT_CorpLogo&quot; value=&quot;Powered by
  --&gt;&lt;!--#set var=&quot;IMG_CorpLogo&quot;

  --&gt;&lt;!--#set var=&quot;ALT_CorpLogo&quot; value=&quot;Powered by
  --&gt;&lt;!--#set var=&quot;IMG_BgImage&quot; value=&quot;http://$SERVER_NAME:$SERVER_PORT/errordocs/BgImage.gif&quot;

  --&gt;&lt;!--#set var=&quot;DOC_Apache&quot; value=&quot;http://$SERVER_NAME:$SERVER_PORT/Apache/&quot;

  --&gt;&lt;!--#if expr=&quot;$anigif&quot; 
  --&gt;&lt;!--#set var=&quot;IMG_Apache&quot; value=&quot;http://$SERVER_NAME:$SERVER_PORT/icons/apache_anim.gif&quot;

  --&gt;&lt;!--#set var=&quot;IMG_Apache&quot; value=&quot;http://$SERVER_NAME:$SERVER_PORT/icons/apache_pb.gif&quot;

  --&gt;&lt;!DOCTYPE HTML PUBLIC &quot;-//IETF//DTD HTML//EN&quot;&gt;
     [&lt;!--#echo var=&quot;REDIRECT_STATUS&quot; --&gt;] &lt;!--#echo
var=&quot;title&quot; --&gt;
   &lt;BODY BGCOLOR=&quot;white&quot; BACKGROUND=&quot;&lt;!--#echo var=&quot;IMG_BgImage&quot;
    &lt;H1 ALIGN=&quot;center&quot;&gt;
     [&lt;!--#echo var=&quot;REDIRECT_STATUS&quot; --&gt;] &lt;!--#echo
var=&quot;title&quot; --&gt;
     &lt;IMG SRC=&quot;&lt;!--#echo var=&quot;IMG_CorpLogo&quot; --&gt;&quot;
          ALT=&quot;&lt;!--#echo var=&quot;ALT_CorpLogo&quot; --&gt;&quot;
    &lt;HR&gt;&lt;!-- ========================================================
   and this is the <SAMP>foot.shtml.en</SAMP> file:
    &lt;DIV ALIGN=&quot;right&quot;&gt;&lt;SMALL&gt;&lt;SUP&gt;Local
Server time:
        &lt;!--#echo var=&quot;DATE_LOCAL&quot; --&gt;
    &lt;DIV ALIGN=&quot;center&quot;&gt;
      &lt;A HREF=&quot;&lt;!--#echo var=&quot;DOC_Apache&quot; --&gt;&quot;&gt;
      &lt;IMG SRC=&quot;&lt;!--#echo var=&quot;IMG_Apache&quot; --&gt;&quot;
BORDER=0 ALIGN=&quot;bottom&quot;
           ALT=&quot;Powered by &lt;!--#echo var=&quot;SERVER_SOFTWARE&quot;
      &lt;SMALL&gt;&lt;SUP&gt;&lt;!--#set var=&quot;var&quot;
       value=&quot;Powered by $SERVER_SOFTWARE -- File last modified on $LAST_MODIFIED&quot;
      --&gt;&lt;!--#echo var=&quot;var&quot; --&gt;&lt;/SUP&gt;&lt;/SMALL&gt;
    &lt;ADDRESS&gt;If the indicated error looks like a misconfiguration, please inform
     &lt;A HREF=&quot;mailto:&lt;!--#echo var=&quot;SERVER_ADMIN&quot;
        SUBJECT=&quot;Feedback about Error message [&lt;!--#echo var=&quot;REDIRECT_STATUS&quot;

          --&gt;] &lt;!--#echo var=&quot;title&quot; --&gt;, req=&lt;!--#echo
var=&quot;REQUEST_URI&quot; --&gt;&quot;&gt;
     &lt;!--#echo var=&quot;SERVER_NAME&quot; --&gt;'s WebMaster&lt;/A&gt;.
  <H3>More welcome!</H3>
  If you have tips to contribute, send mail to <a
  <A HREF="./"><IMG SRC="../images/index.gif" ALT="Index"></A>
  <A HREF="../"><IMG SRC="../images/home.gif" ALT="Home"></A>
  1.19      +8 -0      apache-1.3/htdocs/manual/mod/mod_include.html
  Index: mod_include.html
  RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_include.html,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -u -r1.18 -r1.19
  --- mod_include.html	1998/01/28 19:11:49	1.18
  +++ mod_include.html	1998/02/05 09:58:40	1.19
  @@ -407,6 +407,14 @@
  +<h2>Using Server Side Includes for ErrorDocuments</h2>
  +There is <A HREF="../misc/misc/custom_errordocs.html">a document</A> which
  +describes how to use the features of mod_include to offer internationalized
  +customized server error documents.
   <!--#include virtual="footer.html" -->

View raw message