[Test failure] System.Net.Http.Functional.Tests.PlatformHandler_HttpClientHandler_ServerCertificates_Test.NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds #77726

Activity

2. ghost added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Nov 1, 2022
3. rzikm

   added

   area-System.Net.Http

   on Nov 1, 2022
5. rzikm

   changed the title [-][Test failure] NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds[/-] [+][Test failure] System.Net.Http.Functional.Tests.PlatformHandler_HttpClientHandler_ServerCertificates_Test.NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds[/+] on Nov 1, 2022
6. ManickaP commented on Nov 1, 2022

   

   ManickaP

   on Nov 1, 2022

   Member

   More actions

   Based on the console log, the error is this:

   System.Net.Http.Functional.Tests.PlatformHandler_HttpClientHandler_ServerCertificates_Test.NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds [FAIL]
         System.Net.Http.HttpRequestException : An error occurred while sending the request.
         ---- System.Net.Http.WinHttpException : Error 12175 calling WINHTTP_CALLBACK_STATUS_REQUEST_ERROR, 'A security error occurred'.
         Stack Trace:
              at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
              at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           /_/src/libraries/Common/tests/System/Net/Http/HttpClientHandlerTest.ServerCertificates.cs(234,0): at System.Net.Http.Functional.Tests.HttpClientHandler_ServerCertificates_Test.<NoCallback_RevokedCertificate_NoRevocationChecking_Succeeds>d__19.MoveNext()
           --- End of stack trace from previous location where exception was thrown ---
              at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
              at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           --- End of stack trace from previous location where exception was thrown ---
              at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
              at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           --- End of stack trace from previous location where exception was thrown ---
              at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
              at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
           ----- Inner Stack Trace -----
              at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
           /_/src/libraries/Common/src/System/Threading/Tasks/RendezvousAwaitable.cs(64,0): at System.Threading.Tasks.RendezvousAwaitable`1.GetResult()
           /_/src/libraries/System.Net.Http.WinHttpHandler/src/System/Net/Http/WinHttpHandler.cs(946,0): at System.Net.Http.WinHttpHandler.<StartRequestAsync>d__122.MoveNext()
   

   Docs for 12175 ERROR_WINHTTP_SECURE_FAILURE: One or more errors were found in the Secure Sockets Layer (SSL) certificate sent by the server. To determine what type of error was encountered, check for a WINHTTP_CALLBACK_STATUS_SECURE_FAILURE notification in a status callback function. For more information, see WINHTTP_STATUS_CALLBACK.

   Seems like cert problem, can it be expired? And if I get the description right, does it mean there are more details about the error available? If so, would it be worthwhile to retrieve them?
   cc @wfurt @rzikm
7. wfurt commented on Nov 1, 2022

   

   wfurt

   on Nov 1, 2022

   Member

   More actions

   We should try to reproduce it. If it is expired certificate it will show up consistently.
8. ManickaP

   added this to the 8.0.0 milestone on Nov 1, 2022
9. ghost removed

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Nov 1, 2022
10. ManickaP commented on Nov 1, 2022

    

    ManickaP

    on Nov 1, 2022

    Member

    More actions

    Triage: needs to be tested locally if it's a cert problem (should be easily reproducible). If so, we should promptly fix this or disable the test.
11. wfurt commented on Nov 1, 2022

    

    wfurt

    on Nov 1, 2022

    Member

    More actions

    The test is using https://revoked.badssl.com/ and it expired 10/27. Since this is outer loop test we may ignore it for few more days. The badssl.com usually fix their certs eventually.
    It is still shown as revoked so we may alternatively fix the validation tests to ignore expiration and only check revocation.
    But I'm not sure if it is worth of the troubles.
    Last option IMHO is to remove dependency on badssl.com and host our own sites.
12. wfurt commented on Nov 1, 2022

    

    wfurt

    on Nov 1, 2022

    Member

    More actions

    BTW this is easy to reproduce and SocketsHttpHandler fails as well
13. rzikm

    self-assigned this

    on Nov 2, 2022
14. rzikm commented on Nov 2, 2022

    

    rzikm

    on Nov 2, 2022

    Member

    More actions

    badssl issue: chromium/badssl.com#515

    👍React with 👍1Reacted by Marie Píchová
15. ManickaP

    added

    disabled-testThe test is disabled in source code against the issueThe test is disabled in source code against the issue

    on Jan 31, 2023
16. 8 remaining items

    Load more
17. ghost added

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Mar 8, 2023
18. ghost removed

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Apr 28, 2023
19. ghost added

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Apr 28, 2023
20. ghost removed

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on May 28, 2023
21. wfurt

    modified the milestones: 8.0.0, Future on Jun 7, 2023
22. rzikm

    removed their assignment

    on Jul 20, 2023
23. karelz

    added

    test-run-coreTest failures in .NET Core test runsTest failures in .NET Core test runs

    on Sep 21, 2023
24. rzikm commented on Jan 4, 2024

    

    rzikm

    on Jan 4, 2024

    Member

    More actions

    We should also disable the tests in 7.0 and 6.0 to clean up CI there.
25. karelz commented on Jun 24, 2024

    

    karelz

    on Jun 24, 2024

    Member

    More actions

    Tests were disabled in main (8.0) in PR #79407 and in 7.0.x in PR #96053 and in 6.0.x in PR #96055
26. dotnet-policy-service

    added

    in-prThere is an active PR which will close this issue when it is mergedThere is an active PR which will close this issue when it is merged

    on Aug 1, 2024
27. rzikm

    closed this as completedin #105793on Aug 1, 2024
28. github-actions

    locked and limited conversation to collaborators on Sep 1, 2024
29. karelz

    modified the milestones: Future, 9.0.0 on Sep 3, 2024