In my routes, I use custom message headers to keep track some data. But when one of the steps in the route is a HTTP call (for example calling a web services), all my headers are sent as HTTP headers to the remote HTTP server. This causes the remote HTTP server (which is not under my control) to return a HTTP 404. (One thing I noticed is that the remote HTTP server is perfectly OK with JMS headers, e.g. JMSXGroupID. It just does not like any custom message header that I define.)
I know Camel lets me remove all the headers before going to the http endpoint. But I still need these header data once the http request completes. Any suggestion on how I can use http headers effectively in such situation? Is there an easy way I can stash away these headers and restore them after the http call? I tried to use Exchange properties to keep track of the data. But the data do not survive across routes. Thank you for your help! -- View this message in context: http://camel.465427.n5.nabble.com/Message-headers-and-HTTP-tp5742364.html Sent from the Camel - Users mailing list archive at Nabble.com.
