[thelist] SSI file parsing issues, IIS 4.0

[Madhu Menon]

Ben,

> a number of include files with a .inc extension. I configured the
> Application Mappings for the site so that .inc files are executed with the
> ssinc DDL. The include file virtual paths are all based on a virtual
> directory. Everything works well and all the include files get parsed.

Now, why would you want to do that? You don't need to associate .inc files
with the ssinc DLL at all! The .inc files are the files *that get included*
in the final HTML (or ASP) file. 

> Now today we set up another site on the server, this time with an IP
address
> that is accessible outside our firewall, for the client to view the site.
> The configuration of this site is ostensibly the same as the one that
works,
> and it points to the same files, but on this site the include files are
not
> parsed. When you view the source of the page, you see all the include file
> comment lines, such as <!--#include virtual="/site/includes/header.inc"
-->.

Are your file extensions on the new site any of the following?

.shtml
.stm
.asp
.shtm

These are the only extensions that are parsed by ssinc.dll by default.

If NOT, I'm guessing that what you've done on your first site is ALSO mapped
.htm or .html files to use ssinc.dll but ONLY for that site (as opposed to
changing settings for the whole server)

By default, Win NT/2K is not configured for this. So it's quite possible
that your new site just sees the <!-- #include --> directive as an HTML
comment. 

Go to the new site's properties and check your mappings. You might find the
answer there. 

Regards,

Madhu

<<<   *   >>>
Madhu Menon
Head - User Experience Group
Trisoft Systems Pvt. Ltd.  
Global Software Services

Work: http://www.trisoft.net
Personal: http://madman.weblogs.com 

(forgive the legal crap below)


------------------------DISCLAIMER--------------------------.
The contents of this E-mail (including the contents of the enclosure/(s) or
attachment/(s) if any) are privileged and confidential material of Trisoft
Systems Private Limited and should not be disclosed to, used by or copied in
any manner by anyone other than the intended addressee/(s). If this E-mail
(including the enclosure/(s) or attachment/(s)if any ) has been received in
error, please advise the sender immediately and delete it from your system.
The views expressed in this E-mail message (including the enclosure/(s)or
attachment/(s) if any) are those of the individual sender, except where the
sender expressly, and with authority, states them to be the views of Trisoft
Systems Private Limited.