davsclaus opened a new pull request, #29871: URL: https://github.com/apache/camel/pull/29871
## Backport of #29843 Backport of #29843 (CAMEL-26921: camel-oaipmh - remove the CamelOaimphIgnoreSSLWarnings producer header) to `camel-4.22.x`. **Adapted, not a straight cherry-pick.** On `main`, #29843 builds on #28690 (CAMEL-26130), which made the `CamelOaimphOnlyFirst` and `CamelOaimphIgnoreSSLWarnings` headers apply to their exchange only, and then removes the `CamelOaimphIgnoreSSLWarnings` header. `camel-4.22.x` has neither change: its producer still writes both headers onto the shared endpoint. A patch release should not remove a header, so this backport brings only the per-exchange behaviour to `camel-4.22.x`: - Cherry-picked `00f66540c4ce` (#28690, CAMEL-26130) with `-x`: `OAIPMHProducer` reads `CamelOaimphOnlyFirst` and `CamelOaimphIgnoreSSLWarnings` for the current exchange and no longer writes them onto the endpoint. A message without the header uses the `onlyFirst` and `ignoreSSLWarnings` options of the endpoint. - The removal of the `CamelOaimphIgnoreSSLWarnings` header and the `OAIPMHConstants.IGNORE_SSL_WARNINGS` constant (#29843) is not backported; the header keeps working on `camel-4.22.x`, for its own exchange only. - The upgrade-guide change is left out of this branch: the upgrade guides live on `main`, and the 4.22.3 note goes there in a separate doc-sync PR. - Adds `OAIPMHProducerHeadersPerExchangeTest` from #28690 (four tests, against `MockOaipmhServer` over HTTP and HTTPS). It applies unchanged on `camel-4.22.x`. The Java changes apply to `camel-4.22.x` without conflicts; the only conflict was the 4.24 upgrade guide, which does not exist on this branch and was dropped. JIRA: https://issues.apache.org/jira/browse/CAMEL-26921 (fix version 4.22.3) _Claude Code on behalf of Claus Ibsen (davsclaus)_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
