oscerd commented on issue #1490: URL: https://github.com/apache/camel-kafka-connector/issues/1490#issuecomment-6632193750
Sorry this was never answered. Compression configured on the Kafka side (`compression.type`) is handled by the Kafka clients and brokers, so the sink task always receives decompressed records, and `camel.component.https.contentCompressionDisabled` only turns off the HTTP client's automatic decompression of responses; it does not compress what the connector sends. Custom HTTP headers are supported: any Kafka record header whose name starts with `CamelHeader.` is sent as an HTTP request header without that prefix, so `CamelHeader.X-My-Header` (added for example with Kafka's `InsertHeader` SMT) arrives as `X-My-Header`. To send gzip-compressed bodies on 4.22.x you can add the `camel-zip-deflater` jar matching the connector's Camel version (and its `commons-compress` dependency) to the connector's plugin directory, set `camel.sink.marshal=gzipDeflater` and add a `CamelHeader.Content-Encoding` header with the value `gzip`. Closing this as answered; if any of this does not work on 4.22. x, please open a new issue with your configuration. --- _Claude Code on behalf of Andrea Cosentino_ -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
