Fix for HTTP Configuration Errors using WebScriptEnablingBehavior

I've sufficiently recovered from running the last week-long series covering fixes for WCF to do another one. This week I'll again be covering fixes for WCF that may be hard to find and explaining the details behind each problem.

When using the WebScriptEnablingBehavior to create an AJAX service, the service endpoint is given an accompanying JavaScript proxy endpoint located at the path /js relative to the service endpoint base address. The proxy endpoint allows someone to walk up to the service and obtain information about how to call the service using AJAX.

Since the proxy endpoint is a part of the same application and virtual directory as the service endpoint, the proxy endpoint and service endpoint need to share configuration settings such as security. However, the WebScriptEnablingBehavior was configuring the proxy using a default set of HTTP configuration settings. This caused the proxy endpoint to not work for services that made certain changes to their HTTP configuration.

After installing this fix configuration settings are copied from the HTTP transport configured at the service endpoint to the proxy endpoint to eliminate the configuration error.

This fix is available for download from KB article 972251.