No: “Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non-identity transfer-coding, the Content-Length MUST be ignored.” (RFC 2616, Section 4.4) And no, you can use Content-Length and stream; the protocol doesn’t constrain how your implementation works.
jQuery doesn’t support that, but you can do that with plain XHR: var xhr = new XMLHttpRequest() xhr.open(“GET”, “/test/chunked”, true) xhr.onprogress = function () { console.log(“PROGRESS:”, xhr.responseText) } xhr.send() This works in all modern browsers, including IE 10. W3C specification here. The downside here is that xhr.responseText contains an accumulated response. You can use substring … Read more
OK. I’ve triple-tested this and I am 100% sure that it is being caused by my anti-virus (ESET NOD32 ANTIVIRUS 5). Whenever I disable the Real-Time protection, the issue disappears. Today, I left the Real-Time protection off for 6-7 hours and the issue never occurred. A few moments ago, I switched it back on, only … Read more