oscerd opened a new pull request, #23313: URL: https://github.com/apache/camel/pull/23313
## Backport of #23285 to `camel-4.18.x` Cherry-pick of #23285 (squash `1e776238202e`) onto `camel-4.18.x`, for the **4.18.3** release line. **Original PR:** apache/camel#23285 — CAMEL-23532: camel-vertx-websocket / camel-atmosphere-websocket / camel-iggy - use dedicated HeaderFilterStrategy aligned with sibling components ### Backport notes - **iggy API divergence resolved:** on `camel-4.18.x`, `IggyFetchRecords` uses `message.userHeaders().ifPresent(...)` with `String` keys / `.value()` (vs. main's `Map` / `.toString()` / `.asString()`). The `HeaderFilterStrategy` application was adapted to the 4.18.x shape (filtered per-entry loop inside the `ifPresent` block) rather than taking main's incompatible version. - **Upgrade guide:** the note was placed in `camel-4x-upgrade-guide-4_18.adoc` (the 4_21 guide does not exist on this branch). The matching entry on `main`'s `camel-4x-upgrade-guide-4_18.adoc` is handled in a separate doc-sync PR. - Generated metadata (configurers, URI factories, component & catalog JSON, endpoint-DSL) regenerated against the 4.18.x baseline; unrelated stale-state regen drift reverted. - All three components compile on 4.18.x; `VertxWebsocketHeaderFilterStrategyTest` and `IggyHeaderFilterStrategyTest` pass (4/4 each). ### Original description 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`). vertx-websocket and iggy gain a new `*HeaderFilterStrategy` plus a `headerFilterStrategy` endpoint option; atmosphere-websocket reuses the `HeaderFilterStrategy` it already inherits from the HTTP/servlet stack. --- _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]
