You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Pasquale Congiusti (Jira)" <ji...@apache.org> on 2025/09/10 09:12:00 UTC
[jira] [Resolved] (CAMEL-22403) [camel-google-pubsub] Extend headers with some HeaderFilterStrategy
[ https://issues.apache.org/jira/browse/CAMEL-22403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pasquale Congiusti resolved CAMEL-22403.
----------------------------------------
Resolution: Fixed
> [camel-google-pubsub] Extend headers with some HeaderFilterStrategy
> -------------------------------------------------------------------
>
> Key: CAMEL-22403
> URL: https://issues.apache.org/jira/browse/CAMEL-22403
> Project: Camel
> Issue Type: Improvement
> Affects Versions: 4.14.0
> Reporter: Pasquale Congiusti
> Assignee: Pasquale Congiusti
> Priority: Minor
> Fix For: 4.14.1, 4.15.0
>
>
> The component is now only transferring a few specific headers. However it misses additional headers that can result crucial when integrating with other technologies (ie, telemetry). Given that the component is similar to a queue and the calls are perfomed via http, we should implements a generic transfer of all headers, only filtering those which we're sure are not needed during Camel processing.
> A similar approach as done in camel-jms can serve as a reference, where we have the implementation of an extension of DefaultHeaderFilterStrategy. Ideally we should analyse the protocol to understand which are the be excluded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)