You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short: Multiple Content-Length values found: [58, 58].
So the function sends the json-body to the broker, but sets the HTTP-Header Content-Length twice, which isn't supported by the kafka-channel-dispatcher.
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
I'm trying to setup knative functions with MTChannelBasedBroker based on KafkaChannels.
A Ping-Source is producing events every minute:
My simple function has a subscription to the PingSource-Events:
And generates a new cloudEvent in it's handle-Method, with a json-Body:
But the knative-eventing/kafka-channel-dispatcher rejects the responded events from my function with the following message:
In short:
Multiple Content-Length values found: [58, 58]
.So the function sends the json-body to the broker, but sets the HTTP-Header Content-Length twice, which isn't supported by the kafka-channel-dispatcher.
We guess, it has something to do with the used cloudevents-sdk and the Add on this line.
Versions:
Please have a look at my setup and what I or some part of the knative framework is doing wrong here.
The text was updated successfully, but these errors were encountered: