Hi,
The most likely case here is that it is what error is reporting: service violated http protocol by setting Content-Length response header value, and then writing greater (or lesser) number of bytes to the response output. Often this has something to do with Response.BufferOutput setting, chunking and/or maybe with response compression.
When weird thing happen on the http wire, it's always a good idea to run
Fiddler tool - it's easy to use and extremely helpful when dealing with HTTP problems.
FYI: If you login to the forum, we'll send you email notifications when we post our replies.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.