I don't want to remove entries from MIME lists, I just want to tell IIS to stop serving files with a particular extension.
Why is it so difficult to get IIS to do something so simple as stop serving a file with a particular extension?
I've seen solutions like... add a mapping pointing some some 404.dll, which only exists in some separate lockdown toolkit that claims to be obselete for IIS 6.0+ anyway. I've also read that one can have ASP.NET explicitly forbid serving the file, by creating a mapping to the asp.net handler dll, then specifying the System.Web.HttpForbiddenHandler in the web.config for the filetype. Those work, although at first then forbidden handler didn't appear to work, thanks to the browser cache, LOL: (see answer at http://stackoverflow.com/questions/208571/castleproject-vm-httpforbiddenhandler-not-work).
I'm just looking for a simple solution here.