A client's question about SSI..

Does anyone know how a server "activates" includes?

[Dan_Vendel]

Hi,

This is probably the silliest question this week....

I am trying to make SSI work on a Unix/Red Hat server. It's configured to parse "shtml" which is the extension of my files.

Locally (using Dreamweaver), the include shows just fine, even in "preview". But remotelly, I might as well try to take a bite from my own elbow: It simply doesn't work - and I have tried every possible path: related to document, related to root and absolute paths: no go.

So, I'm curious if there's something going on server-side (or rather: NOT going on). Is there something that "pre-scans" a site for SSI? And if I have upploaded a shtml and try to view it live, it's not yet "registered" as a file to be parsed?

I'm not English spoken and have problems to explain what I after, but I hope you understand what I mean: Is there something beyond my control that's happening?

Thanks for even trying to answer this whimsy post...

Dan

[Dan_Vendel]

Eh...forget about it.
I changed the tag from "include file" to "include virtual" and it's OK.
<embarassed grin />

Dan

[VectorJ]

A server should scan any page that has the .shtml extension; no matter how recently the file has been uploaded. The file is parsed every time it is called by a client.

I would guess that the problem is either a small syntax error like having an extra space in your ssi directive, or maybe a permissions problem if you are trying to execute scripts with ssi.

By the way, your English is better than many native english speaker's. And "taking a bite of my own elbow" is hilarious. :-)

[Dan_Vendel]

Thanks for flatter. :-)
As I wrote: The problem is solved, and I'm ashamed I didn't think about that earlier....

Cheers,
Dan