Added an option to disable type inference from message content #6274
Conversation
This file contains 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
ramonsmits
approved these changes
Feb 17, 2022
timbussmann
force-pushed
the
type-inference-backport
branch
from
ea36504
to
7e9a1f0
Compare
timbussmann
changed the title
DavidBoike
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #6244 (including #6269 )
Allows to opt-out of the default fallback behavior to let the serializer determine the type from the message content. If the
Headers.EnclosedMessageTypesheader does not exist or contains unknown types, NServiceBus invokes the serializer without any type information to let the serializer know that it should try to infer the target type from the message body.Message bodies can contain type information e.g., via XML element names or Newtonsoft.Json's
$typeproperty. The exact behavior of a serializer is not defined and heavily differs between serializer implementations. This can lead to some potential security vulnerability due hard-to-predict impact of user-defined input.This features can disable this fallback behavior which will cause the message to fail processing (and be moved to the error queue).
Documentation: https://docs.particular.net/nservicebus/serialization/#security