Re: Chunking issue with http producer

Hi Bernard, You are right, the patch has nothing to do with if the http endpoint is bridge endpoint or not. I created a JIRA[1] to keep track of this useful feature. [1]https://issues.apache.org/jira/browse/CAMEL-7638 Regards, Willem -- View this message in context: http://camel.465427.n5.

Re: Chunking issue with http producer

Can you please explain why in "Bridge mode *only*" ? >From the doc: "bridgeEndpoint : HttpProducer will ignore the Exchange.HTTP_URI header, and use the endpoint's URI for request" Sorry, but I do the not understand the concrete consequences of using URI x instead of URI y on the opportunity to s

Re: Chunking issue with http producer

Thanks for sharing the solution with us. I think we can enable this kind of feature when the http producer is working in the Bridge mode. -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.co

Re: Chunking issue with http producer

I finally found a solution that i am sharing here for the community. With that proposed patch, the streaming capability is preserved, and the latency is now much better: Here are the details of my patching of "*HttpProducer.java*

Re: Chunking issue with http producer

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 compl

Re: Chunking issue with http producer

If you are using http client 3, it will clean up the input stream when you close the connection. You can find more information by checking the the comments in the doExtractResponseBodyAsStream. That is why we need to cache the input stream as it will be used in the other part of camel route.