Hi Oleg
The problem is that lots of HTTP agents out there (including HttpClient 3.x and HttpClient 4.0) can only handle request / response content streams sequentially. That is, they can start reading response content only after the request content has been fully written out.
This explains the reason clearly..
You can try passing the input stream of the incoming request entity to the outgoing response entity to avoid buffering the entire message content in memory, but I suspect this will not work with many HTTP agents out there, especially for larger content entities.
many thanks asankha
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
