Remove Iot Core specific topic and client id validation checks in MQTT5 #315
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.
$share/<share-name>
to the iot core validation utility functions. Adds testing for the additional functionality.Leaves the validation utility functions intact. We have determined these were not necessary in MQTT5 (and unnecessary client-side validation should always be avoided for future-compatibility reasons) as IoT Core now returns sensible reason codes that help us diagnose these issues (when using MQTT5; MQTT311 continues to be impacted due to the limitations of the spec). We may revisit and use this functionality as an opt-in setting on the 311 client to help prevent/diagnose particular problems.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.