Thanks for your response. Wouldn't it be interesting for next releases to have an option to (not cache and) *defer* the connection closing till the exchange (that is, behind the scene, the input stream of http response) is *effectively* (fully) read ? I am thinking for instance about using a completion callback (via Exchange.addOnCompletion() method) doing the close on that moment...
Bernard. -- View this message in context: http://camel.465427.n5.nabble.com/Chunking-issue-with-http-producer-tp5735075p5735127.html Sent from the Camel - Users mailing list archive at Nabble.com.
