oscerd opened a new pull request, #23285: URL: https://github.com/apache/camel/pull/23285
## CAMEL-23532 Aligns `camel-vertx-websocket`, `camel-atmosphere-websocket` and `camel-iggy` with the `HeaderFilterStrategy` pattern already adopted across the component catalog (CAMEL-23222 `camel-coap`, CAMEL-23507 `camel-cometd`, CAMEL-23515 `camel-nats`). Their inbound consumers previously mapped externally supplied key/value data (WebSocket query/path parameters; Iggy message user-headers) into the Camel message header map without a `HeaderFilterStrategy`. ### Changes - **camel-vertx-websocket** — new `VertxWebsocketHeaderFilterStrategy` (filters `Camel`/`camel` headers case-insensitively, both directions), exposed via a new `headerFilterStrategy` endpoint option; applied in `VertxWebsocketConsumer.populateExchangeHeaders()` before mapping query and path parameters. - **camel-iggy** — new `IggyHeaderFilterStrategy`, exposed via a new `headerFilterStrategy` endpoint option; applied in `IggyFetchRecords` before copying message user-headers. - **camel-atmosphere-websocket** — applies the existing inherited `HttpHeaderFilterStrategy` in `WebsocketConsumer` before mapping query parameters (no new option needed; the component already extends the HTTP/servlet stack). ### Tests - `VertxWebsocketHeaderFilterStrategyTest` and `IggyHeaderFilterStrategyTest`, mirroring `NatsHeaderFilterStrategyTest`. ### Docs - Upgrade-guide note added to `camel-4x-upgrade-guide-4_21.adoc` covering the behaviour change, the new endpoint option, and the opt-out (supply a custom `headerFilterStrategy`). ### Generated artifacts - Regenerated endpoint configurers, URI factories, component & catalog JSON, and endpoint-DSL builder factories for the two components that gained the new option. Fix Version/s on the issue: 4.21.0, 4.18.3, 4.14.8 (`camel-iggy` is main + 4.18.x only — it does not exist on the 4.14.x line). Backports handled separately. --- _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]
