Add option to propagate headers from the incoming message to the outgoing message#2446
Merged
jeremydmiller merged 2 commits intoJasperFx:mainfrom Apr 8, 2026
Merged
Conversation
Adds a PropagateHeadersRule and exposes it via IPolicies.PropagateIncomingHeadersToOutgoing, allowing named headers from an incoming message to be automatically forwarded to all outgoing messages cascaded within the same handler context. Headers not present on the incoming envelope are silently skipped. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This option allows the user to specify a collection of headers which will be copied from the incoming message to any outgoing message in a handler. The headers must first exist on the incoming envelope by adding a custom IEnvelopeMapper which copies them from the transport to the Envelope, because Wolverine does not process custom headers by default.