Re: 404.DLL and default.ida problem
From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: Thu, 15 May 2003 17:47:32 -0700
The 200 looks to be a superficial bug in 404.dll. You'r still OK.
Basically, what your mapping setup did is tell IIS that when you get a .ida
request, execute 404.dll to handle it. 404.dll is an ISAPI which just sends
back a canned 404 response. However, it appears that it did not set the
dwHttpStatusCode to 404 upon completion to notify IIS to log a 404. Default
IIS behavior is to log a 200 for all execution of an ISAPI unless the ISAPI
states otherwise, so you're seeing the 200.
-- //David This posting is provided "AS IS" with no warranties, and confers no rights. // "Rao" <firstname.lastname@example.org> wrote in message news:email@example.com... I observed "GET /default.ida .................. - 200" in IIS log files. So, I updated the machine with latest windows update patches and installed URLLock utility and disabled the mappings ida and idx. I verified that those mappings are done to 404.dll through internet service manager. Re-started the IIS service. Even after that, I can see some of the above HTTP requests still being returned with response code of 200. I expect them to return 404 because of the mappings with 404.dll. Anybody had this problem? --Rao TRN