I came across this problem when testing the latest Aspose.Editor for .NET live demo.

Aspose.Editor is our .NET word processor control. The live demo is an ASP.NET application. The client part is a .NET control that is hosted in an HTML page. It is downloaded and executes in Internet Explorer. The server part is another .NET assembly that runs in an ASP.NET application.

When testing various use cases in the demo on different Windows versions, different Internet Explorer versions and different .NET Framework versions I came across a message box with the following error message:

System.Net.WebException: The server committed a protocol violation. Section=ResponseStatusLine

Looking on the internet it appeared to be quite widespread and a heavily debated topic. We tried several solutions suggested by others including modifying configuration files and so on but it did not help.

The problem only appeared in one configuration and I guessed that the WebResponse classes in the .NET Framework installed on the client machine are responsible for the exception. It looked like a "slightly incorrect" or "non-standard" HTTP response from the server caused problems when it was being parsed by .NET on the client machine.

I've checked we run .NET Framework 2.0 without Service Packs on that machine.

Installing .NET Framework 2.0 Service Pack 1 on the client machine solved the "The server committed a protocol violation." instantly.

Finally, don't forget to check out our Aspose.Editor demo http://www.aspose.com/demos/aspose.editor/default.aspx!