我们使用 .NET Web 服务——非 WCF 和 WCF，尽管由于遗留原因，绝大多数是非 WCF——相当多，而且正如我在 Fiddler，我注意到响应正文非常大。然后我注意到请求标头没有任何 Accept-Encoding 标头。
经过一番挖掘后，发现属性 HttpWebClientProtocol.EnableDecompression 的默认值（所有源自 wsdl.exe 的 WS 存根都派生自该类） .NET BCL 版本之间的更改2.0 和 3.0。我很好奇其中的原因（可能与 WCF 相关），并进一步想知道当您简单地链接到不同的库时是否存在任何其他[相当]基本的变化，这些变化非常安静。
We use .NET Web Services--both non-WCF and WCF, though the overwhelming majority is non-WCF, for legacy reasons--pretty heavily, and as I was testing something in Fiddler, I noticed that the response body size was pretty large. Then I noticed that the request headers didn't have any Accept-Encoding headers.
After doing some digging, it appears that the default value for the property HttpWebClientProtocol.EnableDecompression (from the class of which all wsdl.exe-originated WS stubs derive) changed between .NET BCL versions 2.0 and 3.0. I'm curious as to the reason (which may be WCF-related), and further as to whether there are any other [pretty] fundamental changes that are pretty quiet when you simply link against a different library.
发布评论
评论（1）
看看这个连接< /a> 链接。微软的第一条评论如下：
看来这一变化是由于他们需要修复的错误造成的。
Take a look at this connect link. The first comment from Microsoft states the following:
It looks like the change was a result of a bug that they needed to fix.