urunni88 opened a new pull request, #27787: URL: https://github.com/apache/camel/pull/27787
# Description Fixes [CAMEL-25563](https://issues.apache.org/jira/browse/CAMEL-25563). The camel-http producer sent a header with two or more values as a single line in the form `[a, b]`. It now uses `HttpUtil.applyHeaderValue` (added for CAMEL-25526), so a collection or an object array is sent as one header line per value, as camel-vertx-http, camel-knative-http, camel-netty-http and camel-undertow do. Any other value, including a String with commas, is still sent as one header. Cookies from the cookie handler stay joined with `;`. Tests: - `HttpProducerTwoHeadersWithSameKeyTest` now expects two `to` header lines instead of `[foo, bar]`. - New `HttpProducerMultiValueHeaderTest` covers a List, an array, a String with a comma, and null elements. All camel-http tests pass locally. `HttpOAuth2CachedTokensKeyTest.aCustomResolverReturningNullDoesNotCache` flaked once on Windows and passed on rerun; it is not related to this change. The ticket mentions an entry in the 4.24 upgrade guide. Following CAMEL-25547, I left it out of this PR to avoid conflicts in the guide, but I'm happy to add it here if you prefer. This PR was prepared with AI assistance (Claude); I reviewed and tested all changes. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. -- 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]
