Knative component filters out all headers

[nicolaferraro]

Consider the following integration sending data to a channel:

from('timer:clock?period=3s')
	.setBody().constant("Hello World from Camel K")
	.setHeader('CamelCippaLippa').constant('42')
	.to('log:info?showHeaders=true')
	.to('knative:channel/messages')
	.to('log:info?showHeaders=true')
	.log('sent message to messages channel')

This is the output log:

2019-07-26 10:57:00.318 �[32mINFO �[m [Camel (camel-k) thread #2 - timer://clock] info - Exchange[ExchangePattern: InOnly, Headers: {CamelCippaLippa=42, firedTime=Fri Jul 26 10:57:00 UTC 2019}, BodyType: String, Body: Hello World from Camel K]
2019-07-26 10:57:00.323 �[32mINFO �[m [Camel Thread #3 - NettyClientTCPWorker] info - Exchange[ExchangePattern: InOnly, Headers: {CamelHttpResponseCode=202, CamelHttpResponseText=Accepted, Content-Length=0, Date=Fri, 26 Jul 2019 10:57:00 GMT}, BodyType: byte[], Body: ]
2019-07-26 10:57:00.323 �[32mINFO �[m [Camel Thread #3 - NettyClientTCPWorker] route1 - sent message to messages channel

The CamelCippaLippa header is deleted after passing from the knative endpoint.

[oscerd]

It's netty-http4 component which filter out everything starting with Camel

[lburgazzoli]

I'm going to add options to configure the underlying transport used by the knative component so one can configure the header filter strategy according to the needs