allthingssecurity commented on PR #27690:
URL: https://github.com/apache/camel/pull/27690#issuecomment-6120120328
Pushed c7ec6a285855 on top (no force-push).
1. `Iterable`: fixed in the producer and the reply, see the inline reply.
2. Reply: the blank check is back, and a `Map` / `JsonObject` / `JsonArray`
is one header as in the producer;
tested and documented, see the inline reply.
3. Shared helper: producer and reply now call `HttpUtil.applyHeaderValue`
(camel-support). The method and its 10
unit tests in `HttpUtilTest` are byte for byte the ones in #27689, so
neither PR depends on the other:
`git merge-tree` of the two heads (ee2a700436af, c7ec6a285855), and of
each head on a squash of the other onto
main, is clean and gives one copy.
4. Upgrade guide: the entry has its own heading, `=== camel-knative-http - a
header with several values is sent as
several headers`, after the camel-knative section. The camel-http
sentence is gone. The entry says what changes
for the producer and for the reply, what stays, and how to get the old
single header.
The PR description is rewritten for the final behaviour and has no
camel-http claim; it is the text for the squash
commit. The message of the first commit is unchanged (no force-push).
Tests: `KnativeHttpMultiValueHeaderTest` 18 tests (12 fail on main, 5 with
the previous head); camel-knative-http
194, 0 failures; camel-support 136, 0 failures.
_Claude Code on behalf of allthingssecurity_
--
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]
