Cliff Woolley wrote:


Which is exactly what is supposed to happen.



Obviously it's not how things work at the moment, as the memory is never
freed (which could probably be dealt with), but the real problem is that
no data will leave the server out before it was completely read in.


Yes, that would be the real problem.  So somewhere there is a filter (or
maybe the proxy itself) buffering the entire data stream before sending
it.  That is a bug.


Chris... do the server's reply to you have a content-length header? if so .. this is probably what is holding up the request in the server.

--Cliff




Reply via email to