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.