1) Not running any URL rewrites.
2) using the server's IE to browse, with the local hosts file set to resolve the domain to the IP address of the IIS site. So all access is local.
3) The site's application pool is running under the identity of a created user 'iisservice'. That user has these effective rights to the folder with the index.htm
- traverse/execute
- list folder/read data
- read attributes
- read extended attributes
- create files/write data
- create folders/append data
- read permissions
4) If I change that iisservice user to have full rights to the content folder, the http://mydomain.com or http://mydomain.com/folder still fails with a 404, but http://mydomain.com/index.htm or http://mydomain.com/folder/index.htm works.
5) FRT for http://mydomain.com/folder shows a Request URL of "/folder" (without trailing slash); shows the FIle_cache_access_start of "F:\web\site\folder" (that is the physical location of the index.htm file).
6) URLScan is not installed
7) with directory browsing enabled, a request for http://mydomain.com/folder still shows a 404, does not show a directory listing
8) The 404 page does have the proper physical path, and the requested URL hows http://mydomain.com:80/folder (without trailing slash), although if I http://mydomain.com/folder/ (with a trailing slash), still get a 404.
9) File explorer is set to show extensions, so I know the actual file name is index.htm, not index.htm.txt or something else.
10) the 404 says to look at the FRT and 'see which module is calling SetStatus', but I don't see that module name in the FRT detailed view
Still puzzled....
