Use Content-Length, definitely. The server utilization from this will be almost nonexistent and the benefit to your users will be large. For dynamic content, it’s also quite simple to add compressed response support (gzip). That requires output buffering, which in turn gives you the content length. (not practical with file downloads or already compressed content … Read more
I did some research on this today with an url endpoint accepting letting me configure chunk sizes and intervals. Mac: text/html: image/jpeg: curl 7.24.0 4096 bytes Firefox 17 1024 bytes 1886 bytes Chrome 26.0.1410.65 1024 bytes 1885 bytes Chrome 29.0.1524.0 8 bytes 1885 bytes Safari 6.0.4 (8536.29.13) 1024 bytes whole file Windows XP: IE8 256 … Read more
A PHP response will always be chunked if you don’t specify a content-length header, and a flush occurs. (which will happen automatically after x bytes, just don’t know exactly how much). This is a weird thing to care about. Is this some kind of academic/learning exercise or is there a real world problem you’re trying … 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