From 3ba0aa91f3bc34f69e7953930773e7a700acca38 Mon Sep 17 00:00:00 2001 From: Erik Abele Date: Tue, 5 Nov 2002 19:05:22 +0000 Subject: updated transformations. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97409 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/howto/ssi.html.en | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/manual/howto/ssi.html.en') diff --git a/docs/manual/howto/ssi.html.en b/docs/manual/howto/ssi.html.en index 58b120f7cd..0484511acc 100644 --- a/docs/manual/howto/ssi.html.en +++ b/docs/manual/howto/ssi.html.en @@ -68,12 +68,12 @@ existing HTML documents.

order to give it a .shtml extension, so that those directives would be executed.

-

The other method is to use the XBitHack directive:

+

The other method is to use the XBitHack directive:

XBitHack on

-

XBitHack +

XBitHack 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 @@ -87,7 +87,7 @@ existing HTML documents.

see people recommending that you just tell Apache to parse all .html files for SSI, so that you don't have to mess with .shtml file names. These folks have - perhaps not heard about XBitHack. The thing to + perhaps not heard about XBitHack. 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 -- cgit v1.2.3