-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
InvalidCertificateServers_CertificateValidationDisabled_Succeeds could not resolve expired.badssl.com #63224
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsLooks like badssl.com wasn't available for a period of time. if there's already an issue suggesting we maintain our own endpoint, perhaps this could be duped. BTW since presumably ERROR_WINHTTP_NAME_NOT_RESOLVED is a very common code, perhaps it should have a prettier custom message here...
|
It resolves now but I agree we should look into reducing external dependencies. We now have ability to generate certificate chains in tests (still unstable on macOS). |
Triage:
|
|
Looks like badssl.com wasn't available for a period of time. if there's already an issue suggesting we maintain our own endpoint, perhaps this could be duped.
BTW since presumably ERROR_WINHTTP_NAME_NOT_RESOLVED is a very common code, perhaps it should have a prettier custom message here...
The text was updated successfully, but these errors were encountered: