"SSI" test / Demo Page

There are a lot of configuration options available for how your existing SSI code is handled, you can configure that particular commands be passed though for later SSI execution or that they be ignored. You will need to have a look at "SSI.IH", the header documents a bit and the header is commented, if you need help just ask (dbareis@labyrinth.net.au).

If you have any problems with your SSI, please let me know by sending a sample and the SSI generated html and I will see what I can do to improve the code for the next release.


TEST: #include

Hi this tests included text.


TEST: #echo var="document_name"

The source is called "ssi_in.htm".


TEST: #flastmod & #fsize

This file last modified on Wed Apr 3 2002 at 11:50:23am (2,983 bytes).


TEST: Normal HTML COMMENT!

This line contains a html comment.


TEST: Invalid Cmd "#xinclude"

Command "xinclude" does not exist (will generate warning).
ssi_in.htm(42) - SSI: <!--#xinclude file="2.ih" --> is unsupported!

We have not defined "SSI_LEAVE_UNKNOWN_SSI_TAGS" so the "failing" SSI command (above) is not left in place for SSI to possibly handle but is highlighted in red (this is the default action you can choose to ignore messages or alter the appearance etc).

Also note that it is possible to configure that particular SSI commands be passed through for real SSI processing later or that they be ignored, so if "xinclude" was a real command that could only be executed on the server then you could update the "SSI_CMD_PASSTHROUGH" definition.


TEST: #echo var="http_referer"

SSI command left in place for later execution by SSI on server: "".


TEST: #exec"

SSI command left in place for later execution by SSI on server: "".

Note that PPWIZARD can exec tasks but this is not at "runtime" so we need to pass "exec" though for SSI processing.


Wed Apr 3 2002 at 11:50:53am