Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Mutating forwarded message's headers leaks into incoming headers #5256

Closed
timbussmann opened this issue Aug 31, 2018 · 0 comments · Fixed by #5450
Closed

Mutating forwarded message's headers leaks into incoming headers #5256

timbussmann opened this issue Aug 31, 2018 · 0 comments · Fixed by #5450
Labels
Improvement
Milestone
7.2.0

Comments

@timbussmann
Copy link
Contributor

When mutating headers of a message forwarded using the ForwardCurrentMessageTo API, the header changes are also visible on incoming pipeline (e.g. via IMessageHandlerContext.MessageHeaders.

headers of forwarded messages can't be changed via mutators though and this only works if you write a custom behavior in the RoutingContext or later.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Improvement
Projects
None yet
Milestone
7.2.0
Development

Successfully merging a pull request may close this issue.

Prevent forwarding header manipulations to leak into main pipeline Particular/NServiceBus
2 participants
@SeanFeldman @timbussmann