[GitHub] [camel-k-runtime] nicolaferraro opened a new issue #69: HTTP multi-headers are randomized in camel-knative-http

[GitBox <gi...@apache.org>]

nicolaferraro opened a new issue #69: HTTP multi-headers are randomized in camel-knative-http
URL: https://github.com/apache/camel-k-runtime/issues/69
 
 
   This line https://github.com/apache/camel-k-runtime/blob/72c9d2ae8be188de462ece77493151158da1fd36/camel-knative-http/src/main/java/org/apache/camel/component/knative/http/KnativeHttpComponent.java#L222 behave in a random way when the header contains multiple values.
   
   In case of the header `ce-knativehistory`, values may be like: `channel1.ns.channels.cluster.local; channel2.ns.channels.cluster.local`. They are interpreted by netty as being present multiple times (which is correct) and only one of them is returned by that call (which is correct), but a random one (which is wrong).
   We should find a way to get always the last value of the header, which is the last channel that received the message.
   
   I've tried also to get the full list of values using `getAll` but the order of elements in the list is still randomized.
   
   I've found there's a `CombinedHttpHeader` class in netty that **may** solve the issue by appending values to the same header instead of adding multiple entries, but I'm not able to plug it in Camel Netty.
   
   Any idea @lburgazzoli ?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services