fix: Deserialization checks valid class types for HttpTransportFactory #1882
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.




See b/479228571 for more information.
Attempts to resolve any deserialization issue when trying to create a new HttpTransportFactory. Validates so that a HttpTransportFactory implementation can be created to prevent arbitrary loading of classes (e.g. gadget classes that can execute commands).
Mimics the existing loading behavior in the constructor: