You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[FAIL] AcceptSslCertificatesWithCustomValidationCallbackNSUrlSessionHandler("https://self-signed.badssl.com/") : Status code was not success
[FAIL] AcceptSslCertificatesWithCustomValidationCallbackNSUrlSessionHandler("https://wrong.host.badssl.com/") : Status code was not success
Debugging a bit it seems that these return 404 "Not Found" now, so it seems something changed on badssl.com's side.
We should probably use a different server we control (maybe look into if dotnet/runtime has something we can use?)
The text was updated successfully, but these errors were encountered:
…SessionHandler - fails due to external factors.
The test fails with:
[FAIL] AcceptSslCertificatesWithCustomValidationCallbackNSUrlSessionHandler("https://self-signed.badssl.com/") : Status code was not success
[FAIL] AcceptSslCertificatesWithCustomValidationCallbackNSUrlSessionHandler("https://wrong.host.badssl.com/") : Status code was not success
Debugging a bit it seems that these return 404 "Not Found" now, so it seems something changed on badssl.com's side.
We should probably use a different server we control at some point, but filed
an issue for now (#21912).
…SessionHandler - fails due to external factors. (#21913)
The test fails with:
[FAIL] AcceptSslCertificatesWithCustomValidationCallbackNSUrlSessionHandler("https://self-signed.badssl.com/") : Status code was not success
[FAIL] AcceptSslCertificatesWithCustomValidationCallbackNSUrlSessionHandler("https://wrong.host.badssl.com/") : Status code was not success
Debugging a bit it seems that these return 404 "Not Found" now, so it seems something changed on badssl.com's side.
We should probably use a different server we control at some point, but filed
an issue for now (#21912).
The test fails with:
Debugging a bit it seems that these return 404 "Not Found" now, so it seems something changed on badssl.com's side.
We should probably use a different server we control (maybe look into if dotnet/runtime has something we can use?)
The text was updated successfully, but these errors were encountered: