broken pipe message when ExtensionsFilter is serving resources to Internet Explorer

When using Microsoft Internet Explorer with some tomahawk components that have resources served by the ExtensionsFilter, ugly "broken pipe" error messages get output to the log, although the page actually works ok. This problem appears particularly common for the Tomahawk inputCalendar in popup mode.

The cause is stupidity on the part of IE, as usual. It is starting requests for resources, then just closing the socket. Of course the ExtensionsFilter then gets a write exception when writing data to the socket, and reports this as an error.

I think the problem is triggered when javascript creates multiple DOM nodes with the same resource; IE then makes a concurrent request for each one but when the first request completes it then cancels the other (redundant) requests by just closing its socket.

The fix is to just ignore write failures; if the client has closed its socket then that is its problem, not ours.