Danny, For the purposes of SSI, <!-- and --> are not indicative of comments (neither is the #). However, the comment tags do prevent what would be a SSI command from being rendered in a browser if the page is served without SSI enabled. None of the example includes I gave are client side - they are server side (hence Server Side Include) just like <RCinclude/filetoinclude.ext> is. See the SSI documentation (http://localhost/syshelp/ssi.htm) for clarification and examples.
-Jeff -----Original Message----- From: Danny Mallory [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 02:46 PM To: sambar List Member Subject: [sambar] header {07} So is this commented #include a client side directive ???? Danny On 27/Jan/2003 07:03:50, Jeff Adams wrote: > At 08:01 AM 01/27/2003 +0100, Henk Schrik wrote: > > >At 01:07 27-1-2003 +0100, you wrote: > >>I would think long and hard about adding .htm to your ssi config > >>thats a huge waste of resource. > >Maybe something to eleborate to the unknown like me ???? (also using > >.htm in ssi). > > The extensions defined as SSI are parsed by the SSI engine for SSI > commands. Defining "regular" extensions (e.g. htm, html) as SSI extensions > means that every document served must also be pre-parsed for commands > before it is served. Hence the use of a "special" extension (i.e. shtml) > that indicates a document that should be SSI parsed before serving. You > can include just about any kind of file without adding it to the SSI > extensions list. The example below could create an entire document without > adding htm, c, html, or stm to the SSI list. > > <BODY> > <!--#include virtual="menu.htm" --> > <!--#include virtual="gamenews.c" --> > <!--#include virtual="availablegames.html" --> > <!--#include virtual="sitefooter.stm" --> > </BODY> > > -Jeff ------------------------------------------------------- To unsubscribe please go to http://www.sambar.ch/list/
