Unify headers and values in tables containing TLS version. #82
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
…ces which can result in savings higher than what was spend.
|
@microsoft-github-policy-service agree company="ndaal Ges.f. Sicherheit in der Informationstechnik mbH & Co. KG" |
|
Hello, thanks for the update, really helpful |
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.
So far ARI did use inconsistent headers and values across different resource Types, e.g. for the headers the following version were found:
They have all been changed to the uniform version "Minimum TLS Version".
Further the values received were sometimes being given as "TLS1_1", "tlsv1_1", "TLS 1.2", ...
An attempt to unify these is made by using the replace-method.