add SEC_E_CONTEXT_EXPIRED to avoid throwing InternalException #79129
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
|
Tagging subscribers to this area: @dotnet/ncl, @vcsjones Issue Detailscontributes to #66188 This is not fix for the underlying issue - since there is no clear repro at the moment.
|
stephentoub
approved these changes
Dec 2, 2022
rzikm
approved these changes
Dec 5, 2022
|
test failure unrelated. |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
contributes to #66188
In the linked issue we would throw internal exception because we don't have mapping for the error.
This is not fix for the underlying issue - since there is no clear repro at the moment.
At least, it would bubble up as Win32Exception as other Schannel errors.