TLS 1.0 support for .NET 3.x on Unity 2018.2+ #443
Merged
Conversation
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
mamoonraja
approved these changes
Aug 24, 2018
…ough for unhandled URLs, Added warning to use US South instance or .NET 4.6
|
🎉 This PR is included in version 2.8.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Summary
This pull request adds changes for .NET 3.x support in Unity 2018.2 and above. Some platforms do not support .NET 4.x so we cannot push users to the TLS 1.2 endpoint if they are using Unity 2018.2. Additionally we only add TLS 1.1 and TLS 1.2 protocols if the user is using .NET 4.x there is no support for TLS 1.1 and 1.2 in .NET 3.x.