Hi folks,
I'm curious - can anyone explain what actually happens internally if you
try to read more from $r-read() than specified in the Content-Length
header?
I noticed when trying subsequent calls to read after all bytes had been
read that it truncates the buffer, which I guess is
On Tue, Apr 22, 2008 at 10:51 AM, John ORourke
[EMAIL PROTECTED] wrote:
I'm curious - can anyone explain what actually happens internally if you
try to read more from $r-read() than specified in the Content-Length
header?
What used to happen is it would hang the process forever. Not sure if