[In order for any reply to be added to the PR database, ] [you need to include <[EMAIL PROTECTED]> in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ]
Synopsis: no response from the ssi function State-Changed-From-To: open-feedback State-Changed-By: coar State-Changed-When: Fri Jun 12 02:57:05 PDT 1998 State-Changed-Why: I don't think it will make any difference, but put a space before the SSI closure - that is, change <!--#echo var="LAST_MODIFIED"--> to <!--#echo var="LAST_MODIFIED" --> This is recommended practice in general. What do you see when you go to the SSI-enhanced page? Any "[an error occurred...]" messages, or are the SSIs just being ignored. What do you see if you View Source of the rendered page? If the viewed source includes the raw SSI directives, the page is definitely not getting parsed. What happens if you go explicitly to the page (i.e., to "/index.shtml") rather than just to the directory object (i.e., "/")? Does your DirectoryIndex line include "index.shtml" as one of the files to try? Release-Changed-From-To: 1.3-1.3.0 Release-Changed-By: coar Release-Changed-When: Fri Jun 12 02:57:05 PDT 1998
