You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2002/09/16 03:49:39 UTC
cvs commit: httpd-2.0/docs/manual/howto ssi.xml ssi.html.en
rbowen 2002/09/15 18:49:39
Modified: docs/manual/howto ssi.html.en
Added: docs/manual/howto ssi.xml
Log:
Conversion of ssi.html to xml
Revision Changes Path
1.15 +116 -230 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.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- ssi.html.en 16 Sep 2002 00:04:34 -0000 1.14
+++ ssi.html.en 16 Sep 2002 01:49:39 -0000 1.15
@@ -1,110 +1,14 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta name="generator" content="HTML Tidy, see www.w3.org" />
-
- <title>Apache Tutorial: Introduction to Server Side
- Includes</title>
- </head>
- <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
-
- <body bgcolor="#FFFFFF" text="#000000" link="#0000FF"
- vlink="#000080" alink="#FF0000">
- <!--#include virtual="header.html" -->
-
- <h1 align="center">Apache Tutorial: Introduction to Server Side
- Includes</h1>
- <a id="__index__" name="__index__"></a> <!-- INDEX BEGIN -->
-
-
- <ul>
- <li><a
- href="#apachetutorial:introductiontoserversideincludes">Apache
- Tutorial: Introduction to Server Side Includes</a></li>
-
- <li><a href="#whataressi">What are SSI?</a></li>
-
- <li><a href="#configuringyourservertopermitssi">Configuring
- your server to permit SSI</a></li>
-
- <li>
- <a href="#basicssidirectives">Basic SSI directives</a>
-
- <ul>
- <li><a href="#todaysdate">Today's date</a></li>
-
- <li><a href="#modificationdateofthefile">Modification
- date of the file</a></li>
-
- <li><a href="#includingtheresultsofacgiprogram">Including
- the results of a CGI program</a></li>
- </ul>
- </li>
-
- <li>
- <a href="#additionalexamples">Additional examples</a>
-
- <ul>
- <li><a href="#whenwasthisdocumentmodified">When was this
- document modified?</a></li>
-
- <li><a href="#includingastandardfooter">Including a
- standard footer</a></li>
-
- <li><a href="#whatelsecaniconfig">What else can I
- config?</a></li>
-
- <li><a href="#executingcommands">Executing
- commands</a></li>
- </ul>
- </li>
-
- <li>
- <a href="#advancedssitechniques">Advanced SSI
- techniques</a>
-
- <ul>
- <li><a href="#settingvariables">Setting
- variables</a></li>
-
- <li><a href="#conditionalexpressions">Conditional
- expressions</a></li>
- </ul>
- </li>
-
- <li><a href="#conclusion">Conclusion</a></li>
- </ul>
- <!-- INDEX END -->
- <hr />
-
- <h2><a id="apachetutorial:introductiontoserversideincludes"
- name="apachetutorial:introductiontoserversideincludes">Apache
- Tutorial: Introduction to Server Side Includes</a></h2>
-
- <table border="1">
- <tr>
- <td valign="top"><strong>Related Modules</strong><br />
- <br />
- <a href="../mod/mod_include.html">mod_include</a><br />
- <a href="../mod/mod_cgi.html">mod_cgi</a><br />
- <a href="../mod/mod_expires.html">mod_expires</a><br />
- </td>
-
- <td valign="top"><strong>Related Directives</strong><br />
- <br />
- <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/core.html#setoutputfilter">SetOutputFilter</a><br />
- <a
- href="../mod/mod_setenvif.html#BrowserMatchNoCase">BrowserMatchNoCase</a><br />
- </td>
- </tr>
- </table>
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ --><title>Apache Tutorial: Introduction to Server Side Includes - Apache HTTP Server</title><link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" /><link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" /><link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" /><link href="../images/favicon.ico" rel="shortcut icon" /></head><body id="manual-page"><div id="page-header"><p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p><p class="apache">Apache HTTP Server Version 2.0</p><img alt="" src="../images/feather.gif" /></div><div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div><div id="path"><a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs-project/">Documentation</a> > <a href="../">Version 2.0</a></div><div id="page-content"><div id="preamble"><h1>Apache Tutorial: Introduction to Server Side Includes</h1>
+<p>Server-side includes provide a means to add dynamic content to
+existing HTML documents.</p>
+</div><div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#related">Introduction</a></li><li><img alt="" src="../images/down.gif" /> <a href="#what">What are SSI?</a></li><li><img alt="" src="../images/down.gif" /> <a href="#configuring">Configuring your server to permit SSI</a></li><li><img alt="" src="../images/down.gif" /> <a href="#basic">Basic SSI directives</a></li><li><img alt="" src="../images/down.gif" /> <a href="#additionalexamples">Additional examples</a></li><li><img alt="" src="../images/down.gif" /> <a href="#config">What else can I config?</a></li><li><img alt="" src="../images/down.gif" /> <a href="#exec">Executing commands</a></li><li><img alt="" src="../images/down.gif" /> <a href="#advanced">Advanced SSI techniques</a></li><li><img alt="" src="../images/down.gif" /> <a href="#conclusion">Conclusion</a></li></ul></div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="related" id="related">Introduction</a></h2>
+ <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td><ul><li><code class="module"><a href="../mod/mod_include.html">mod_include</a></code></li><li><code class="module"><a href="../mod/mod_cgi.html">mod_cgi</a></code></li><li><code class="module"><a href="../mod/mod_expires.html">mod_expires</a></code></li></ul></td><td><ul><li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li><li><code class="directive"><a href="../mod/mod_include.html#xbithack">XBitHack</a></code></li><li><code class="directive"><a href="../mod/mod_mime.html#addtype">AddType</a></code></li><li><code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code></li><li><code class="directive"><a href="../mod/mod_setenvif.html#browsermatchnocase">BrowserMatchNoCase</a></code></li></ul></td></tr></table>
<p>This article deals with Server Side Includes, usually called
simply SSI. In this article, I'll talk about configuring your
@@ -114,9 +18,8 @@
<p>In the latter part of the article, we'll talk about some of
the somewhat more advanced things that can be done with SSI,
such as conditional statements in your SSI directives.</p>
- <hr />
- <h2><a id="whataressi" name="whataressi">What are SSI?</a></h2>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="what" id="what">What are SSI?</a></h2>
<p>SSI (Server Side Includes) are directives that are placed in
HTML pages, and evaluated on the server while the pages are
@@ -132,22 +35,19 @@
But if a majority of your page is being generated at the time
that it is served, you need to look for some other
solution.</p>
- <hr />
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="configuring" id="configuring">Configuring your server to permit SSI</a></h2>
- <h2><a id="configuringyourservertopermitssi"
- name="configuringyourservertopermitssi">Configuring your server
- to permit SSI</a></h2>
<p>To permit SSI on your server, you must have the following
directive either in your <code>httpd.conf</code> file, or in a
<code>.htaccess</code> file:</p>
-<pre>
+<div class="example"><p><code>
Options +Includes
-</pre>
+</code></p></div>
<p>This tells Apache that you want to permit files to be parsed
for SSI directives. Note that most configurations contain
- multiple <a href="../mod/core.html#options">Options</a> directives
+ multiple <code class="directive"><a href="../mod/core.html#options">Options</a></code> directives
that can override each other. You will probably need to apply the
<code>Options</code> to the specific directory where you want SSI
enabled in order to assure that it gets evaluated last.</p>
@@ -157,10 +57,10 @@
do this. You can tell Apache to parse any file with a
particular file extension, such as <code>.shtml</code>, with
the following directives:</p>
-<pre>
- AddType text/html .shtml
+<div class="example"><p><code>
+ AddType text/html .shtml<br />
AddOutputFilter INCLUDES .shtml
-</pre>
+</code></p></div>
<p>One disadvantage to this approach is that if you wanted to
add SSI directives to an existing page, you would have to
@@ -168,26 +68,26 @@
order to give it a <code>.shtml</code> extension, so that those
directives would be executed.</p>
- <p>The other method is to use the <code>XBitHack</code>
- directive:</p>
-<pre>
+ <p>The other method is to use the <code class="directive"><a href="../mod/mod_includes.html#xbithack">XBitHack</a></code> directive:</p>
+<div class="example"><p><code>
XBitHack on
-</pre>
+</code></p></div>
- <p><code>XBitHack</code> tells Apache to parse files for SSI
+ <p><code class="directive"><a href="../mod/mod_includes.html#xbithack">XBitHack</a></code>
+ tells Apache to parse files for SSI
directives if they have the execute bit set. So, to add SSI
directives to an existing page, rather than having to change
the file name, you would just need to make the file executable
using <code>chmod</code>.</p>
-<pre>
+<div class="example"><p><code>
chmod +x pagename.html
-</pre>
+</code></p></div>
<p>A brief comment about what not to do. You'll occasionally
see people recommending that you just tell Apache to parse all
<code>.html</code> files for SSI, so that you don't have to
mess with <code>.shtml</code> file names. These folks have
- perhaps not heard about <code>XBitHack</code>. The thing to
+ perhaps not heard about <code class="directive"><a href="../mod/mod_includes.html#xbithack">XBitHack</a></code>. The thing to
keep in mind is that, by doing this, you're requiring that
Apache read through every single file that it sends out to
clients, even if they don't contain any SSI directives. This
@@ -209,21 +109,17 @@
only at the date of the originally requested file, ignoring
the modification date of any included files.</li>
- <li>Use the directives provided by <a
- href="../mod/mod_expires.html">mod_expires</a> to set an
- explicit expiration time on your files, thereby letting
- browsers and proxies know that it is acceptable to cache
- them.</li>
+ <li>Use the directives provided by
+ <code class="module"><a href="../mod/mod_expires.html">mod_expires</a></code> to set an explicit expiration
+ time on your files, thereby letting browsers and proxies
+ know that it is acceptable to cache them.</li>
</ol>
- <hr />
-
- <h2><a id="basicssidirectives" name="basicssidirectives">Basic
- SSI directives</a></h2>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="basic" id="basic">Basic SSI directives</a></h2>
<p>SSI directives have the following syntax:</p>
-<pre>
+<div class="example"><p><code>
<!--#element attribute=value attribute=value ... -->
-</pre>
+</code></p></div>
<p>It is formatted like an HTML comment, so if you don't have
SSI correctly enabled, the browser will ignore it, but it will
@@ -236,11 +132,11 @@
series. For now, here are some examples of what you can do with
SSI</p>
- <h3><a id="todaysdate" name="todaysdate">Today's
- date</a></h3>
-<pre>
+<h3><a name="todaysdate" id="todaysdate">Today's date</a></h3>
+
+<div class="example"><p><code>
<!--#echo var="DATE_LOCAL" -->
-</pre>
+</code></p></div>
<p>The <code>echo</code> element just spits out the value of a
variable. There are a number of standard variables, which
@@ -251,43 +147,43 @@
<p>If you don't like the format in which the date gets printed,
you can use the <code>config</code> element, with a
<code>timefmt</code> attribute, to modify that formatting.</p>
-<pre>
- <!--#config timefmt="%A %B %d, %Y" -->
+
+<div class="example"><p><code>
+ <!--#config timefmt="%A %B %d, %Y" --><br />
Today is <!--#echo var="DATE_LOCAL" -->
-</pre>
+</code></p></div>
+
+
+<h3><a name="lastmodified" id="lastmodified">Modification date of the file</a></h3>
- <h3><a id="modificationdateofthefile"
- name="modificationdateofthefile">Modification date of the
- file</a></h3>
-<pre>
+<div class="example"><p><code>
This document last modified <!--#flastmod file="index.html" -->
-</pre>
+</code></p></div>
<p>This element is also subject to <code>timefmt</code> format
configurations.</p>
- <h3><a id="includingtheresultsofacgiprogram"
- name="includingtheresultsofacgiprogram">Including the results
- of a CGI program</a></h3>
+
+<h3><a name="cgi" id="cgi">Including the results of a CGI program</a></h3>
<p>This is one of the more common uses of SSI - to output the
results of a CGI program, such as everybody's favorite, a ``hit
counter.''</p>
-<pre>
+
+<div class="example"><p><code>
<!--#include virtual="/cgi-bin/counter.pl" -->
-</pre>
- <hr />
+</code></p></div>
+
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="additionalexamples" id="additionalexamples">Additional examples</a></h2>
- <h2><a id="additionalexamples"
- name="additionalexamples">Additional examples</a></h2>
<p>Following are some specific examples of things you can do in
your HTML documents with SSI.</p>
<hr />
- <h2><a id="whenwasthisdocumentmodified"
- name="whenwasthisdocumentmodified">When was this document
- modified?</a></h2>
+<h3><a name="docmodified" id="docmodified">When was this document
+modified?</a></h3>
<p>Earlier, we mentioned that you could use SSI to inform the
user when the document was most recently modified. However, the
@@ -295,10 +191,10 @@
following code, placed in your HTML document, will put such a
time stamp on your page. Of course, you will have to have SSI
correctly enabled, as discussed above.</p>
-<pre>
- <!--#config timefmt="%A %B %d, %Y" -->
+<div class="example"><p><code>
+ <!--#config timefmt="%A %B %d, %Y" --><br />
This file last modified <!--#flastmod file="ssi.shtml" -->
-</pre>
+</code></p></div>
<p>Of course, you will need to replace the
<code>ssi.shtml</code> with the actual name of the file that
@@ -306,19 +202,18 @@
looking for a generic piece of code that you can paste into any
file, so you probably want to use the
<code>LAST_MODIFIED</code> variable instead:</p>
-<pre>
- <!--#config timefmt="%D" -->
+<div class="example"><p><code>
+ <!--#config timefmt="%D" --><br />
This file last modified <!--#echo var="LAST_MODIFIED" -->
-</pre>
+</code></p></div>
<p>For more details on the <code>timefmt</code> format, go to
your favorite search site and look for <code>strftime</code>. The
syntax is the same.</p>
- <hr />
- <h2><a id="includingastandardfooter"
- name="includingastandardfooter">Including a standard
- footer</a></h2>
+
+<h3><a name="footer" id="footer">Including a standard footer</a></h3>
+
<p>If you are managing any site that is more than a few pages,
you may find that making changes to all those pages can be a
@@ -338,35 +233,35 @@
attribute is probably more useful, and should specify a URL
relative to the document being served. It can start with a /,
but must be on the same server as the file being served.</p>
-<pre>
+<div class="example"><p><code>
<!--#include virtual="/footer.html" -->
-</pre>
+</code></p></div>
<p>I'll frequently combine the last two things, putting a
<code>LAST_MODIFIED</code> directive inside a footer file to be
included. SSI directives can be contained in the included file,
and includes can be nested - that is, the included file can
include another file, and so on.</p>
- <hr />
- <h2><a id="whatelsecaniconfig" name="whatelsecaniconfig">What
- else can I config?</a></h2>
+
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="config" id="config">What else can I config?</a></h2>
+
<p>In addition to being able to <code>config</code> the time
format, you can also <code>config</code> two other things.</p>
<p>Usually, when something goes wrong with your SSI directive,
you get the message</p>
-<pre>
+<div class="example"><p><code>
[an error occurred while processing this directive]
-</pre>
+</code></p></div>
<p>If you want to change that message to something else, you
can do so with the <code>errmsg</code> attribute to the
<code>config</code> element:</p>
-<pre>
+<div class="example"><p><code>
<!--#config errmsg="[It appears that you don't know how to use SSI]" -->
-</pre>
+</code></p></div>
<p>Hopefully, end users will never see this message, because
you will have resolved all the problems with your SSI
@@ -377,10 +272,8 @@
can specify <code>bytes</code> for a full count in bytes, or
<code>abbrev</code> for an abbreviated number in Kb or Mb, as
appropriate.</p>
- <hr />
-
- <h2><a id="executingcommands"
- name="executingcommands">Executing commands</a></h2>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="exec" id="exec">Executing commands</a></h2>
+
<p>I expect that I'll have an article some time in the coming
months about using SSI with small CGI programs. For now, here's
@@ -389,18 +282,18 @@
shell (<code>/bin/sh</code>, to be precise - or the DOS shell,
if you're on Win32). The following, for example, will give you
a directory listing.</p>
-<pre>
- <pre>
- <!--#exec cmd="ls" -->
+<div class="example"><p><code>
+ <pre><br />
+ <!--#exec cmd="ls" --><br />
</pre>
-</pre>
+</code></p></div>
<p>or, on Windows</p>
-<pre>
- <pre>
- <!--#exec cmd="dir" -->
+<div class="example"><p><code>
+ <pre><br />
+ <!--#exec cmd="dir" --><br />
</pre>
-</pre>
+</code></p></div>
<p>You might notice some strange formatting with this directive
on Windows, because the output from <code>dir</code> contains
@@ -415,33 +308,30 @@
feature disabled. You can allow SSI, but not the
<code>exec</code> feature, with the <code>IncludesNOEXEC</code>
argument to the <code>Options</code> directive.</p>
- <hr />
+ </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="advanced" id="advanced">Advanced SSI techniques</a></h2>
- <h2><a id="advancedssitechniques"
- name="advancedssitechniques">Advanced SSI techniques</a></h2>
<p>In addition to spitting out content, Apache SSI gives you
the option of setting variables, and using those variables in
comparisons and conditionals.</p>
- <h3><a id="caveat" name="caveat">Caveat</a></h3>
+<h3><a name="caveat" id="caveat">Caveat</a></h3>
<p>Most of the features discussed in this article are only
available to you if you are running Apache 1.2 or later. Of
course, if you are not running Apache 1.2 or later, you need to
upgrade immediately, if not sooner. Go on. Do it now. We'll
wait.</p>
- <hr />
- <h2><a id="settingvariables" name="settingvariables">Setting
- variables</a></h2>
+
+<h3><a name="variables" id="variables">Setting variables</a></h3>
<p>Using the <code>set</code> directive, you can set variables
for later use. We'll need this later in the discussion, so
we'll talk about it here. The syntax of this is as follows:</p>
-<pre>
+<div class="example"><p><code>
<!--#set var="name" value="Rich" -->
-</pre>
+</code></p></div>
<p>In addition to merely setting values literally like that,
you can use any other variable, including, for example,
@@ -450,16 +340,16 @@
to give values to your variables. You will specify that
something is a variable, rather than a literal string, by using
the dollar sign ($) before the name of the variable.</p>
-<pre>
+<div class="example"><p><code>
<!--#set var="modified" value="$LAST_MODIFIED" -->
-</pre>
+</code></p></div>
<p>To put a literal dollar sign into the value of your
variable, you need to escape the dollar sign with a
backslash.</p>
-<pre>
+<div class="example"><p><code>
<!--#set var="cost" value="\$100" -->
-</pre>
+</code></p></div>
<p>Finally, if you want to put a variable in the midst of a
longer string, and there's a chance that the name of the
@@ -468,13 +358,13 @@
variable in braces, to remove this confusion. (It's hard to
come up with a really good example of this, but hopefully
you'll get the point.)</p>
-<pre>
+<div class="example"><p><code>
<!--#set var="date" value="${DATE_LOCAL}_${DATE_GMT}" -->
-</pre>
- <hr />
+</code></p></div>
+
+
+<h3><a name="conditional" id="conditional">Conditional expressions</a></h3>
- <h2><a id="conditionalexpressions"
- name="conditionalexpressions">Conditional expressions</a></h2>
<p>Now that we have variables, and are able to set and compare
their values, we can use them to express conditionals. This
@@ -486,12 +376,12 @@
actual page.</p>
<p>The structure of this conditional construct is:</p>
-<pre>
- <!--#if expr="test_condition" -->
- <!--#elif expr="test_condition" -->
- <!--#else -->
+<div class="example"><p><code>
+ <!--#if expr="test_condition" --><br />
+ <!--#elif expr="test_condition" --><br />
+ <!--#else --><br />
<!--#endif -->
-</pre>
+</code></p></div>
<p>A <em>test_condition</em> can be any sort of logical
comparison - either comparing values to one another, or testing
@@ -503,10 +393,10 @@
<p>In your configuration file, you could put the following
line:</p>
-<pre>
- BrowserMatchNoCase macintosh Mac
+<div class="example"><p><code>
+ BrowserMatchNoCase macintosh Mac<br />
BrowserMatchNoCase MSIE InternetExplorer
-</pre>
+</code></p></div>
<p>This will set environment variables ``Mac'' and
``InternetExplorer'' to true, if the client is running Internet
@@ -514,13 +404,13 @@
<p>Then, in your SSI-enabled document, you might do the
following:</p>
-<pre>
- <!--#if expr="${Mac} && ${InternetExplorer}" -->
- Apologetic text goes here
- <!--#else -->
- Cool JavaScript code goes here
+<div class="example"><p><code>
+ <!--#if expr="${Mac} && ${InternetExplorer}" --><br />
+ Apologetic text goes here<br />
+ <!--#else --><br />
+ Cool JavaScript code goes here<br />
<!--#endif -->
-</pre>
+</code></p></div>
<p>Not that I have anything against IE on Macs - I just
struggled for a few hours last week trying to get some
@@ -533,15 +423,11 @@
<code>SetEnvIf</code> directives, and other related directives,
this functionality can let you do some pretty involved dynamic
stuff without ever resorting to CGI.</p>
- <hr />
- <h2><a id="conclusion" name="conclusion">Conclusion</a></h2>
+</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div><div class="section"><h2><a name="conclusion" id="conclusion">Conclusion</a></h2>
<p>SSI is certainly not a replacement for CGI, or other
technologies used for generating dynamic web pages. But it is a
great way to add small amounts of dynamic content to pages,
without doing a lot of extra work.</p>
- <!--#include virtual="footer.html" -->
- </body>
-</html>
-
+</div></div><div id="footer"><p class="apache">Maintained by the <a href="http://httpd.apache.org/docs-project/">Apache HTTP Server Documentation Project</a></p><p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div></body></html>
\ No newline at end of file
1.1 httpd-2.0/docs/manual/howto/ssi.xml
Index: ssi.xml
===================================================================
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?>
<manualpage>
<relativepath href=".."/>
<title>Apache Tutorial: Introduction to Server Side Includes</title>
<summary>
<p>Server-side includes provide a means to add dynamic content to
existing HTML documents.</p>
</summary>
<section id="related"><title>Introduction</title>
<related>
<modulelist>
<module>mod_include</module>
<module>mod_cgi</module>
<module>mod_expires</module>
</modulelist>
<directivelist>
<directive module="core">Options</directive>
<directive module="mod_include">XBitHack</directive>
<directive module="mod_mime">AddType</directive>
<directive module="core">SetOutputFilter</directive>
<directive module="mod_setenvif">BrowserMatchNoCase</directive>
</directivelist>
</related>
<p>This article deals with Server Side Includes, usually called
simply SSI. In this article, I'll talk about configuring your
server to permit SSI, and introduce some basic SSI techniques
for adding dynamic content to your existing HTML pages.</p>
<p>In the latter part of the article, we'll talk about some of
the somewhat more advanced things that can be done with SSI,
such as conditional statements in your SSI directives.</p>
</section>
<section id="what"><title>What are SSI?</title>
<p>SSI (Server Side Includes) are directives that are placed in
HTML pages, and evaluated on the server while the pages are
being served. They let you add dynamically generated content to
an existing HTML page, without having to serve the entire page
via a CGI program, or other dynamic technology.</p>
<p>The decision of when to use SSI, and when to have your page
entirely generated by some program, is usually a matter of how
much of the page is static, and how much needs to be
recalculated every time the page is served. SSI is a great way
to add small pieces of information, such as the current time.
But if a majority of your page is being generated at the time
that it is served, you need to look for some other
solution.</p>
</section>
<section id="configuring">
<title>Configuring your server to permit SSI</title>
<p>To permit SSI on your server, you must have the following
directive either in your <code>httpd.conf</code> file, or in a
<code>.htaccess</code> file:</p>
<example>
Options +Includes
</example>
<p>This tells Apache that you want to permit files to be parsed
for SSI directives. Note that most configurations contain
multiple <directive module="core">Options</directive> directives
that can override each other. You will probably need to apply the
<code>Options</code> to the specific directory where you want SSI
enabled in order to assure that it gets evaluated last.</p>
<p>Not just any file is parsed for SSI directives. You have to
tell Apache which files should be parsed. There are two ways to
do this. You can tell Apache to parse any file with a
particular file extension, such as <code>.shtml</code>, with
the following directives:</p>
<example>
AddType text/html .shtml<br />
AddOutputFilter INCLUDES .shtml
</example>
<p>One disadvantage to this approach is that if you wanted to
add SSI directives to an existing page, you would have to
change the name of that page, and all links to that page, in
order to give it a <code>.shtml</code> extension, so that those
directives would be executed.</p>
<p>The other method is to use the <directive
module="mod_includes">XBitHack</directive> directive:</p>
<example>
XBitHack on
</example>
<p><directive module="mod_includes">XBitHack</directive>
tells Apache to parse files for SSI
directives if they have the execute bit set. So, to add SSI
directives to an existing page, rather than having to change
the file name, you would just need to make the file executable
using <code>chmod</code>.</p>
<example>
chmod +x pagename.html
</example>
<p>A brief comment about what not to do. You'll occasionally
see people recommending that you just tell Apache to parse all
<code>.html</code> files for SSI, so that you don't have to
mess with <code>.shtml</code> file names. These folks have
perhaps not heard about <directive
module="mod_includes">XBitHack</directive>. The thing to
keep in mind is that, by doing this, you're requiring that
Apache read through every single file that it sends out to
clients, even if they don't contain any SSI directives. This
can slow things down quite a bit, and is not a good idea.</p>
<p>Of course, on Windows, there is no such thing as an execute
bit to set, so that limits your options a little.</p>
<p>In its default configuration, Apache does not send the last
modified date or content length HTTP headers on SSI pages,
because these values are difficult to calculate for dynamic
content. This can prevent your document from being cached, and
result in slower perceived client performance. There are two
ways to solve this:</p>
<ol>
<li>Use the <code>XBitHack Full</code> configuration. This
tells Apache to determine the last modified date by looking
only at the date of the originally requested file, ignoring
the modification date of any included files.</li>
<li>Use the directives provided by
<module>mod_expires</module> to set an explicit expiration
time on your files, thereby letting browsers and proxies
know that it is acceptable to cache them.</li>
</ol>
</section>
<section id="basic"><title>Basic SSI directives</title>
<p>SSI directives have the following syntax:</p>
<example>
<!--#element attribute=value attribute=value ... -->
</example>
<p>It is formatted like an HTML comment, so if you don't have
SSI correctly enabled, the browser will ignore it, but it will
still be visible in the HTML source. If you have SSI correctly
configured, the directive will be replaced with its
results.</p>
<p>The element can be one of a number of things, and we'll talk
some more about most of these in the next installment of this
series. For now, here are some examples of what you can do with
SSI</p>
<section id="todaysdate"><title>Today's date</title>
<example>
<!--#echo var="DATE_LOCAL" -->
</example>
<p>The <code>echo</code> element just spits out the value of a
variable. There are a number of standard variables, which
include the whole set of environment variables that are
available to CGI programs. Also, you can define your own
variables with the <code>set</code> element.</p>
<p>If you don't like the format in which the date gets printed,
you can use the <code>config</code> element, with a
<code>timefmt</code> attribute, to modify that formatting.</p>
<example>
<!--#config timefmt="%A %B %d, %Y" --><br />
Today is <!--#echo var="DATE_LOCAL" -->
</example>
</section>
<section id="lastmodified"><title>Modification date of the file</title>
<example>
This document last modified <!--#flastmod file="index.html" -->
</example>
<p>This element is also subject to <code>timefmt</code> format
configurations.</p>
</section>
<section id="cgi"><title>Including the results of a CGI program</title>
<p>This is one of the more common uses of SSI - to output the
results of a CGI program, such as everybody's favorite, a ``hit
counter.''</p>
<example>
<!--#include virtual="/cgi-bin/counter.pl" -->
</example>
</section>
</section>
<section id="additionalexamples">
<title>Additional examples</title>
<p>Following are some specific examples of things you can do in
your HTML documents with SSI.</p>
<hr />
<section id="docmodified"><title>When was this document
modified?</title>
<p>Earlier, we mentioned that you could use SSI to inform the
user when the document was most recently modified. However, the
actual method for doing that was left somewhat in question. The
following code, placed in your HTML document, will put such a
time stamp on your page. Of course, you will have to have SSI
correctly enabled, as discussed above.</p>
<example>
<!--#config timefmt="%A %B %d, %Y" --><br />
This file last modified <!--#flastmod file="ssi.shtml" -->
</example>
<p>Of course, you will need to replace the
<code>ssi.shtml</code> with the actual name of the file that
you're referring to. This can be inconvenient if you're just
looking for a generic piece of code that you can paste into any
file, so you probably want to use the
<code>LAST_MODIFIED</code> variable instead:</p>
<example>
<!--#config timefmt="%D" --><br />
This file last modified <!--#echo var="LAST_MODIFIED" -->
</example>
<p>For more details on the <code>timefmt</code> format, go to
your favorite search site and look for <code>strftime</code>. The
syntax is the same.</p>
</section>
<section id="footer">
<title>Including a standard footer</title>
<p>If you are managing any site that is more than a few pages,
you may find that making changes to all those pages can be a
real pain, particularly if you are trying to maintain some kind
of standard look across all those pages.</p>
<p>Using an include file for a header and/or a footer can
reduce the burden of these updates. You just have to make one
footer file, and then include it into each page with the
<code>include</code> SSI command. The <code>include</code>
element can determine what file to include with either the
<code>file</code> attribute, or the <code>virtual</code>
attribute. The <code>file</code> attribute is a file path,
<em>relative to the current directory</em>. That means that it
cannot be an absolute file path (starting with /), nor can it
contain ../ as part of that path. The <code>virtual</code>
attribute is probably more useful, and should specify a URL
relative to the document being served. It can start with a /,
but must be on the same server as the file being served.</p>
<example>
<!--#include virtual="/footer.html" -->
</example>
<p>I'll frequently combine the last two things, putting a
<code>LAST_MODIFIED</code> directive inside a footer file to be
included. SSI directives can be contained in the included file,
and includes can be nested - that is, the included file can
include another file, and so on.</p>
</section>
</section>
<section id="config">
<title>What else can I config?</title>
<p>In addition to being able to <code>config</code> the time
format, you can also <code>config</code> two other things.</p>
<p>Usually, when something goes wrong with your SSI directive,
you get the message</p>
<example>
[an error occurred while processing this directive]
</example>
<p>If you want to change that message to something else, you
can do so with the <code>errmsg</code> attribute to the
<code>config</code> element:</p>
<example>
<!--#config errmsg="[It appears that you don't know how to use SSI]" -->
</example>
<p>Hopefully, end users will never see this message, because
you will have resolved all the problems with your SSI
directives before your site goes live. (Right?)</p>
<p>And you can <code>config</code> the format in which file
sizes are returned with the <code>sizefmt</code> attribute. You
can specify <code>bytes</code> for a full count in bytes, or
<code>abbrev</code> for an abbreviated number in Kb or Mb, as
appropriate.</p>
</section>
<section id="exec">
<title>Executing commands</title>
<p>I expect that I'll have an article some time in the coming
months about using SSI with small CGI programs. For now, here's
something else that you can do with the <code>exec</code>
element. You can actually have SSI execute a command using the
shell (<code>/bin/sh</code>, to be precise - or the DOS shell,
if you're on Win32). The following, for example, will give you
a directory listing.</p>
<example>
<pre><br />
<!--#exec cmd="ls" --><br />
</pre>
</example>
<p>or, on Windows</p>
<example>
<pre><br />
<!--#exec cmd="dir" --><br />
</pre>
</example>
<p>You might notice some strange formatting with this directive
on Windows, because the output from <code>dir</code> contains
the string ``<<code>dir</code>>'' in it, which confuses
browsers.</p>
<p>Note that this feature is exceedingly dangerous, as it will
execute whatever code happens to be embedded in the
<code>exec</code> tag. If you have any situation where users
can edit content on your web pages, such as with a
``guestbook'', for example, make sure that you have this
feature disabled. You can allow SSI, but not the
<code>exec</code> feature, with the <code>IncludesNOEXEC</code>
argument to the <code>Options</code> directive.</p>
</section>
<section id="advanced">
<title>Advanced SSI techniques</title>
<p>In addition to spitting out content, Apache SSI gives you
the option of setting variables, and using those variables in
comparisons and conditionals.</p>
<section id="caveat"><title>Caveat</title>
<p>Most of the features discussed in this article are only
available to you if you are running Apache 1.2 or later. Of
course, if you are not running Apache 1.2 or later, you need to
upgrade immediately, if not sooner. Go on. Do it now. We'll
wait.</p>
</section>
<section id="variables"><title>Setting variables</title>
<p>Using the <code>set</code> directive, you can set variables
for later use. We'll need this later in the discussion, so
we'll talk about it here. The syntax of this is as follows:</p>
<example>
<!--#set var="name" value="Rich" -->
</example>
<p>In addition to merely setting values literally like that,
you can use any other variable, including, for example,
environment variables, or some of the variables we discussed in
the last article (like <code>LAST_MODIFIED</code>, for example)
to give values to your variables. You will specify that
something is a variable, rather than a literal string, by using
the dollar sign ($) before the name of the variable.</p>
<example>
<!--#set var="modified" value="$LAST_MODIFIED" -->
</example>
<p>To put a literal dollar sign into the value of your
variable, you need to escape the dollar sign with a
backslash.</p>
<example>
<!--#set var="cost" value="\$100" -->
</example>
<p>Finally, if you want to put a variable in the midst of a
longer string, and there's a chance that the name of the
variable will run up against some other characters, and thus be
confused with those characters, you can place the name of the
variable in braces, to remove this confusion. (It's hard to
come up with a really good example of this, but hopefully
you'll get the point.)</p>
<example>
<!--#set var="date" value="${DATE_LOCAL}_${DATE_GMT}" -->
</example>
</section>
<section id="conditional">
<title>Conditional expressions</title>
<p>Now that we have variables, and are able to set and compare
their values, we can use them to express conditionals. This
lets SSI be a tiny programming language of sorts.
<code>mod_include</code> provides an <code>if</code>,
<code>elif</code>, <code>else</code>, <code>endif</code>
structure for building conditional statements. This allows you
to effectively generate multiple logical pages out of one
actual page.</p>
<p>The structure of this conditional construct is:</p>
<example>
<!--#if expr="test_condition" --><br />
<!--#elif expr="test_condition" --><br />
<!--#else --><br />
<!--#endif -->
</example>
<p>A <em>test_condition</em> can be any sort of logical
comparison - either comparing values to one another, or testing
the ``truth'' of a particular value. (A given string is true if
it is nonempty.) For a full list of the comparison operators
available to you, see the <code>mod_include</code>
documentation. Here are some examples of how one might use this
construct.</p>
<p>In your configuration file, you could put the following
line:</p>
<example>
BrowserMatchNoCase macintosh Mac<br />
BrowserMatchNoCase MSIE InternetExplorer
</example>
<p>This will set environment variables ``Mac'' and
``InternetExplorer'' to true, if the client is running Internet
Explorer on a Macintosh.</p>
<p>Then, in your SSI-enabled document, you might do the
following:</p>
<example>
<!--#if expr="${Mac} && ${InternetExplorer}" --><br />
Apologetic text goes here<br />
<!--#else --><br />
Cool JavaScript code goes here<br />
<!--#endif -->
</example>
<p>Not that I have anything against IE on Macs - I just
struggled for a few hours last week trying to get some
JavaScript working on IE on a Mac, when it was working
everywhere else. The above was the interim workaround.</p>
<p>Any other variable (either ones that you define, or normal
environment variables) can be used in conditional statements.
With Apache's ability to set environment variables with the
<code>SetEnvIf</code> directives, and other related directives,
this functionality can let you do some pretty involved dynamic
stuff without ever resorting to CGI.</p>
</section>
</section>
<section id="conclusion"><title>Conclusion</title>
<p>SSI is certainly not a replacement for CGI, or other
technologies used for generating dynamic web pages. But it is a
great way to add small amounts of dynamic content to pages,
without doing a lot of extra work.</p>
</section>
</manualpage>