Disable PostAsyncExpect100Continue_FailsAfterContentSendStarted_Throws on non-Sockets...

Commit migrated from https://github.com/dotnet/corefx/commit/a010364670e9a5a8df39d3d7eac97f0e129aaaa1

diff --git a/src/libraries/System.Net.Http/tests/FunctionalTests/HttpRetryProtocolTests.cs b/src/libraries/System.Net.Http/tests/FunctionalTests/HttpRetryProtocolTests.cs
index b177460..e069963 100644 (file)
--- a/src/libraries/System.Net.Http/tests/FunctionalTests/HttpRetryProtocolTests.cs
+++ b/src/libraries/System.Net.Http/tests/FunctionalTests/HttpRetryProtocolTests.cs
@@ -68,9 +68,11 @@ namespace System.Net.Http.Functional.Tests
         [Fact]
         public async Task PostAsyncExpect100Continue_FailsAfterContentSendStarted_Throws()
         {
-            if (IsWinHttpHandler)
+            if (!UseSocketsHttpHandler)
             {
                 // WinHttpHandler does not support Expect: 100-continue.
+                // And the test is expecting specific behaviors of how SocketsHttpHandler does pooling;
+                // it generally works on CurlHandler, but not always.
                 return;
             }