From 57fb682075d1d0a2136f3b438cde6154f3efd623 Mon Sep 17 00:00:00 2001 From: Stephen Toub Date: Thu, 9 May 2019 17:24:31 -0400 Subject: [PATCH] Disable PostAsyncExpect100Continue_FailsAfterContentSendStarted_Throws on non-SocketsHttpHandler (dotnet/corefx#37553) Commit migrated from https://github.com/dotnet/corefx/commit/a010364670e9a5a8df39d3d7eac97f0e129aaaa1 --- .../System.Net.Http/tests/FunctionalTests/HttpRetryProtocolTests.cs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) 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 --- 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; } -- 2.7.4