Why the http response in chunked transfer-encoding is only for some clients

Question

I have an asp.net mvc application running on IIS 7. The problem I am facing is that depending on the client, the response can be restored (as seen through the violinist) as "chunked transfer-encoding". why does this happen only with some of my clients (even if two computers are on the same network with the same browser (IE 8), and not all, or vice versa?

Can anyone explain this to me?

Sorry for this latest update, but the problem was the result of the user reaching the server. If the user was connected to the local LAN via a vpn connection, the proxy server would be bypassed, otherwise the proxy server would be used. This led to two different results.

Answer 1

Blocked coding is allowed on the server side if you prematurely flush the output stream. Do you have any user agent specific code that can call Flush ()?

Answer 2

RFC 2616 says :

HTTP/1.1 ""

Transfer-Encoding: chunked HTTP/1.1. HTTP/1.0 () 0,9? , .

HTTP/1.1, 1.0 ( - 1.1). , 1.1, 1.0, .

: MSIE 6+ " " - Advanced - HTTP 1.1 settings - "Use HTTP 1.1" "Use HTTP 1.1 through proxy connections".

, - , Content-Length .