Helpful Information
 
 
Category: Windows Help
What's up with IIS 5.0

Just a general interest query; what causes IIS to return a 404 error after any SSI calls after an #exec command?

E.g.
<!--#include virtual="blah.shtml"-->
<!--#exec cgi="blah.cgi"-->

blah.shtml will be called fine
blah.cgi will be called fine

However:
<!--#exec cgi="blah.cgi"-->
<!--#include virtual="blah.shtml"-->

blah.cgi will be called and work
blah.shtml will return a '404' error.

Which is a bit of a pain because I like to test out php scripts etc. on it before I upload it to a apache server. (A necessary evil, as I don't always have access to the internet.)

Anyone got a clue?

'm not sure how ssi finishes its work, but it might be that script does not exit properly causing the rest of code on your page to misbehave. Is it all to your code or is there something else? and whats in cgi script?

It can be a simple php file also that causes this problem

E.g.

<? phpinfo(); ?>

Well hidden away in the windows setup, under iis and web services...an option to serve SSI

http://www.microsoft.com/resources/documentation/WindowsServ/2003/standard/proddocs/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/standard/proddocs/en-us/gs_installingiis.asp

do a search for shtml on that page....










privacy (GDPR)