If you don’t want to expose some camel header as the Http header, you can do it with camel header filter[1][2], in this way, you application logic cannot affect the camel internal logic.
[1]http://camel.apache.org/maven/camel-2.14.0/camel-core/apidocs/org/apache/camel/spi/HeaderFilterStrategy.html [2]http://camel.apache.org/how-to-avoid-sending-some-or-all-message-headers.html -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 8, 2014 at 8:22:04 AM, Minh Tran ([email protected]) wrote: > Hi > > I've run into an issue where my route clears the headers right before a rest > call to prevent > unintended headers being sent on the request. Something like this. > > > > > > Unfortunately this seems to wipe out the CamelRedeliveryCounter as well. So > when an > error occurs, redelivery just continues forever. I had to exclude Camel* > headers to > prevent this from happening. > > Was there any reason why this wasn't put into properties instead or at least > there should > be a warning on the removeHeaders documentation that to remove all headers > would mess > up redelivery attempts.
