If I may, please allow me to recommend perusing the documentation a bit. I
notice you've been having a lot of problems, and while some are undoubtedly
due to bugs in the product, others, like this one, could be resolved with a
Ctrl-F and search for keywords in the docs.
*.shtml is an "implicit mapping," like /servlet and *.jsp. It's defined
globally, and can be overridden locally, but to totally disable it you've
got to comment it out in global.properties. JRun has limited SSI
capability. It can handle virtual includes and <servlet> tags, but not much
else. So if you need to have Apache handle the SSI directives, you should
disable that mapping in JRun.
In my experience, not that many people need/want to use JRun's SSI
capability. I also think it should be configurable from the JMC (and it may
be in the future, along with the other implicit mappings), but for now it's
in there and you have to change it by editing the properties manually.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: Matt Senter [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 09, 2000 1:31 PM
> To: Jrun-Talk@Houseoffusion. Com
> Subject: SHTML files
>
>
> JRun just doesn't seem to like .shtml files. I have to comment out the
> ssi-filter for my servers for my Sites to function properly.
> What is JRun
> attempting to do with these files, and why doesn't it work?
> For example, for
> Sites sharing the same IP as virtualhosts, each index.shtml page will
> forward to the index page of one particular Site. Any help would be
> appreciated.
>
> Thanks,
> -Matt
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
