Thanks, I will give it a try. Do you know if there is some concern using exchange properties that I should worry about, perhaps with multi-threading?
Best regards, Alex soto > On Nov 10, 2015, at 2:57 PM, Daniel Lamb <dan...@discoverygarden.ca> wrote: > > Store the headers as properties on the exchange before filtering them out. > Then you can pull them back out after you get your response from the remote > server and do what you need to do. > > ~Danny > > On Nov 10, 2015, at 3:52 PM, Alex Soto <alex.s...@envieta.com> wrote: > >> In case its not clear, I need my custom headers for after the HTTP request >> comes back, I just don’t want these headers to go out to the remote server. >> Currently, I am using a headerFilterStrategy, but that seems to remove the >> headers entirely, as opposed to filter them, as the name implies. >> >> Best regards, >> Alex soto >> >> >> >>> On Nov 10, 2015, at 2:30 PM, Alex Soto <alex.s...@envieta.com> wrote: >>> >>> Hello, >>> >>> I have a route with some custom headers that I need to preserve after >>> sending an HTTP client request (HTTP producer), however, I do not want >>> these headers to be sent as HTTP headers to the remote server. >>> >>> Is there a way to accomplish this? >>> >>> Best regards, >>> Alex soto >>> >>> >>> >> >
