简体繁体中英

WCF Content-Length mismatch when using IIS Compression

原文 2016-05-11 05:18:53 6 1 c#/ wcf/ iis

I have an issue where if I enable dynamic content compression in IIS 7.5, I get a different content length. I know this could happen since the data is being compressed but the problem is it is actually bigger.

Before After

I know there are related posts like this one but the solutions are often modules modifying the content-length. In this example, I ruled that out by using a simple demo WCF app but I still get an incorrect content length. IF you think I missed the correct question / answer, just let me know.

WCF service returns incorrect Content-Length when using gzip encoding

Here is the solution of the demo wcf I am using. https://github.com/janmchan/WCFDemo.git

1 answers

As it turns out, there was nothing wrong with the response. Using fiddler, I could see the saw response as the compressed version and it seems that the length corresponds to the length of those characters. So our conclusion is that the end system receiving this does not know how to handle the compressed response. I'll keep this answer open for debate until we have confirmed that this is the case.

FileResult content-length mismatch

UpdatePanel async request hangs when there is a content-length mismatch

Response Content-length mismatch when running Vue SPA in .Net Core App

Response Content-Length mismatch: too few bytes written

getting content-length using sockets

“Fiddler has detected a protocol violation in session. Content-Length mismatch”

WebResponse Content-Length Returns -1

IIS 7 managed module can't get Content-Length or bytes sent

Azure BlobBaseClient.OpenReadAsync() leads to: System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (...)

HTTP HEAD response - set Content-Length

暂无

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

Related Question FileResult content-length mismatch UpdatePanel async request hangs when there is a content-length mismatch Response Content-length mismatch when running Vue SPA in .Net Core App Response Content-Length mismatch: too few bytes written getting content-length using sockets “Fiddler has detected a protocol violation in session. Content-Length mismatch” WebResponse Content-Length Returns -1 IIS 7 managed module can't get Content-Length or bytes sent Azure BlobBaseClient.OpenReadAsync() leads to: System.InvalidOperationException: Response Content-Length mismatch: too few bytes written (...) HTTP HEAD response - set Content-Length

Related Tags

WCF Content-Length mismatch when using IIS Compression

Question

1 answers

solution1 0 ACCPTED 2016-05-11 23:39:35

solution1
0 ACCPTED 2016-05-11 23:39:35