Increased verbosity on SSL authentication exceptions#59
Merged
andyburke merged 1 commit intoandyburke:masterandyburke/UnityHTTP:masterfrom Jan 4, 2016
adrianrudnik:undetailed-https-exceptionCopy head branch name to clipboard
Merged
Increased verbosity on SSL authentication exceptions#59andyburke merged 1 commit intoandyburke:masterandyburke/UnityHTTP:masterfrom adrianrudnik:undetailed-https-exceptionCopy head branch name to clipboard
andyburke merged 1 commit intoandyburke:masterandyburke/UnityHTTP:masterfrom
adrianrudnik:undetailed-https-exceptionCopy head branch name to clipboard
Conversation
andyburke
added a commit
that referenced
this pull request
Jan 4, 2016
Increased verbosity on SSL authentication exceptions
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Currently we will only see an "Exception: The authentication or decryption has failed." message, like in #58. With the new change it is more verbose, giving the user a correct hint on what went wrong like
CryptographicException: Unsupported hash algorithm: 1.2.840.113549.1.1.13Also the code currently assumed Unity without the otherwise used if directive.