Hi Jeeze -B, I appreciate your earlier suggestion (that is, using *.jsp files instead of the *.shtml equivalent), however according to the TC 4.1 release notes - SSI How to (http://jakarta.apache.org/tomcat/tomcat-4.1-doc/ssi-howto.html ) : [ Introduction: > 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. > Within Tomcat SSI support can be added when using Tomcat as your HTTP > server and you require SSI support. Typically this is done during > development when you don't want to run a web server like Apache.Tomcat SSI > support implements the same SSI directives as Apache. See the <A >HREF="http://httpd.apache.org/docs/howto/ssi.html#basicssidirectives";>Apache > Introduction to SSI</A> for information on using SSI directives.SSI support is > implemented using the servlet class org.apache.catalina.ssi.SSIServlet. > Traditionally, this servlet is mapped to the URL pattern "*.shtml". > > Installation: > > >> CAUTION - SSI directives can be used to execute programs external to the >> Tomcat JVM. If you are using the Java SecurityManager this will bypass >> your security policy configuration in catalina.policy. Rename >> $CATALINA_BASE/server/lib/servlets-ssi.renametojar to >> $CATALINA_BASE/server/lib/servlets-ssi.jar.Remove the XML comments from >> around the SSI servlet and servlet-mapping configuration in >> $CATALINA_BASE/conf/web.xml. > ]
There is no indication in reference to the above that SSI under TC 4.1, without using *.jsp files shouldn't work. All indications are that *.shtml files and for that matter the <servlet> tag is suported! I would very much appreciate it if somebody could throw more light on this matter - It is a question most people seem try to avoid answering. Any further suggestion(s) would be much appreciated. Bob.
