It's noted in many of the http components (http4, for example) that the component will copy the In message headers to the Out message headers. It's also documented as an example that camel can be used as a proxy bridge from one HTTP endpoint to another. There are posts that recommend that folks make use of removeHeaders() or extending a header filter strategy for known headers. In the case where you are proxying to an http resource where you don't know or even care what most of the headers are in the request (the client can pretty much send whatever they want), how can you prevent these request headers from being copied and subsequent returned to the client? Typical proxies don't return request headers as a response to the client, and camel as a proxy (by example given) shouldn't either.
I don't understand the statement that 'in headers are copied to out headers to preserve routing'. The http4 component isn't tampering with in headers in the exchange (is it?) so how would not copying the headers prevent the next component in a route from being able to work with the exchange? Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/http-proxying-and-headerfiltering-tp5768641.html Sent from the Camel - Users mailing list archive at Nabble.com.
