We already have a removeHeaders() DSL [1], but I +1 Matt's idea about header namespaces and header management altogether.
I find HeaderFilterStrategies essential to avoid leaking implementation details to external services in the form of transport headers. Just relying on components to rightfully prefix their metadata with CamelHttp*, CamelMongo*, etc. will be insufficient if we want to provide better ways for handling and manipulation. There has to be a cleverer way, and I think Matt is on the right path here with his proposal. Regards, Raúl. [1] http://camel.apache.org/how-to-remove-the-http-protocol-headers-in-the-camel-message.html Sent while on the move On 23 Mar 2013 21:32, "Henryk Konsek" <hekon...@gmail.com> wrote: > Hi, > > > For 3.0.. Have there been any discussions about possible improvement on > how the > > headers and properties work across the components? > > +1, I like the idea. > > I'd like to have possibility to drop/retain headers base on the > regular expression. For example: > > from(...).dropHeaders(regExp("HTTP.*")).to(...); > > Maybe we could provide dropHeaders/retainHeaders DSL element taking > the expression as an argument? > > Best regards. > > -- > Henryk Konsek > http://henryk-konsek.blogspot.com >
