Invalid request fails to serve 404 Error when extension is mapped to ssinc.dll

shane.mulhall — Wed, 04 Feb 2009 06:44:47 GMT

Hi all,

Firstly thanks for all the contributors - both problem raisers and resolvers - where I have leveraged solutions from this site in the past.

Problem Symptom:

Non existent URI of static content with a valid path within it fails to respond with a 404 error.

E.g.

http://127.0.0.1/index.htm exists and returns successfully
http://127.0.0.1/index.htm/<Anything> does not exist but returns the content of index.htm
http://127.0.0.1/index.htm/ also returns the content of index.htm as does any further suffixing to http://127.0.0.1/index.htm/
http://127.0.0.1/SomeNonExistentPage fails with a 404 as expected

Irrespective of the address, if there is a valid partial address within the first part of the URI then the content of that valid address is served.

This symptom only occurs for static content. Requests to traditional .ASP content do not exhibit the above behaviour.

We have .htm and.html pages mapped to ssinc.dll because we have a large volume of legacy content that includes .htm(l) resources.

If .htm(l) mapping to ssinc.dll is NOT configured, then the symptom expressed in point 2 above does not occur; however the included content (#include file=...) is not retrieved and published - as expected.

We are at a total loss to find the reason for this. WFetch, WGet, etc reveal the 200 OK response so it's not a browser issue.

Briefly the environment is:

Win 2003 Standard Edition
IIS 6

Note that we have another similar server environment that exhibits the exact same behaviour.

SSI Server Side Includes -- Not working as advertised

sdeliasr — Wed, 14 Nov 2007 22:35:31 GMT

I'm trying to use SSI and am finding that the include statement is being treated as a comment. I can see it in "View Source" intact, the same as in the source file.

I've tried this under WinXP Pro and Windows Server 2003. Under the latter, I went into "Web Service Extensions" and allowed SSI.

Inside IIS, the virtual directory is taking the defaults that shows that the .shtml file extension points to the ssinc.dll

I know that this works with ASP pages, but I need to get it to work with an .html file as the "parent" page that is including a .shtml file.

I can send/show the sample code I'm using if that would help.

I've been googling and searching this issue like crazy and still haven't found anything close to explaining this.

Thanks in advance!

Steve Delia

Search results matching tag 'ssi server side include'

Invalid request fails to serve 404 Error when extension is mapped to ssinc.dll

SSI Server Side Includes -- Not working as advertised