The basic connection has been closed: Does the server submit an HTTP protocol conflict?

The basic connection has been closed: the server submitted an HTTP protocol conflict.

This usually happens when we use the. net http component to access some Internet URL resources.
However, it is found that it is okay to use WinHTTP encapsulation to read data and return normal results. However, it is always uncomfortable to use Com for hosted native components. But I don't know where the problem is? Feeling, it must be the same as the http implementation of. net.CodeBecause the reading of COM components is normal for the same URL (the com era has passed the test). However, not all URLs have similar faults, generally, some dynamic Asp.net pages are more likely to appear.

 

Recently I finally found out that Microsoft has a kb discussion:

Http://forums.microsoft.com/MSDN/ShowPost.aspx? Postid = 296969 & siteid = 1

 

Specifically, add
<Configuration>

......
<System.net>
<Settings>
<Httpwebrequest useunsafeheaderparsing = "true"/>
</Settings>
</System.net>
</Configuration>

It turns out that the HTTP protocol may not end with a CRLF, which is strictly implemented. net HTTP protocol components are captured, and the question is wrong. In fact, most HTTP protocol components in the com era can be ignored. To ignore the native components of. net, the above configuration overwrites the system's machine. config default settings.

Capital-based ICP filing