Skip to content

The MessageReceiverContext must support raw byte[] for headers as well #9191

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
artembilan opened this issue May 28, 2024 · 0 comments
Closed

Comments

@artembilan
Copy link
Member

More info in Spring Cloud Stream issue: spring-cloud/spring-cloud-stream#2905

@artembilan artembilan added this to the 6.4.0-M1 milestone May 28, 2024
spring-builds pushed a commit that referenced this issue Jun 7, 2024
Fixes: #9191

Not all inbound protocol handlers convert header from native representation.
Sometimes they just come in as `byte[]`.

* Fix `MessageReceiverContext` to support `byte[]` for headers used in the observation,
e.g. `B3-*`, `traceparent` etc.

(cherry picked from commit b29ff9a)
spring-builds pushed a commit that referenced this issue Jun 7, 2024
Fixes: #9191

Not all inbound protocol handlers convert header from native representation.
Sometimes they just come in as `byte[]`.

* Fix `MessageReceiverContext` to support `byte[]` for headers used in the observation,
e.g. `B3-*`, `traceparent` etc.

(cherry picked from commit b29ff9a)
EddieChoCho pushed a commit to EddieChoCho/spring-integration that referenced this issue Jun 26, 2024
…eceiverContext`

Fixes: spring-projects#9191

Not all inbound protocol handlers convert header from native representation.
Sometimes they just come in as `byte[]`.

* Fix `MessageReceiverContext` to support `byte[]` for headers used in the observation,
e.g. `B3-*`, `traceparent` etc.

**Auto-cherry-pick to `6.3.x` & `6.2.x`**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants