I have a subweb (marked as an application in IIS) that I do >>not<< want to utilize an httpHandler
defined in the parent web.
According to the documentation, I should be able to do this by putting the following directive in
the subweb's web.config file:
<httpHandlers>
<remove verb="*" path="*.scef" />
</httpHandlers>
But that doesn't work unless you first make the parent web's application dll -- where the handler is
defined -- available to the subweb (I did this by copying the parent dll into the subweb's bin
directory...which is stupid, but it works).
I've seen reference to this being a known bug in ASP.NET.
I'd like confirmation that this is a known bug. I'd also appreciate hearing if there are any other
workarounds other than the one I stumbled across.
- Mark