C#HttpClient远程主机强行关闭了现有连接

问题描述

我正在使用他们的托管页面集成来与替代付款进行集成.他们的C#SDK目前没有可用的集成，但是您可以看到它很简单，我制作了一个小类来发送发布请求并获取JSON响应.

I'm working on an integration with Alternative Payments using their hosted page integration. Their C# SDK does not have this integration available at the moment, but as you can see it's pretty simple and I made a small class to send the post request and get the JSON response.

我测试了我在PostMan和cURL上发送的json对象，它们都可以工作，也可以使用身份验证标头，所以我认为这不是问题.这是我的课程的构造函数:

I tested the json object I'm sending on PostMan and cURL and both work, also the authentication header, so I think they are not the problem. Here is the constructor of my class:

public AlternativePaymentsCli(string apiSecretKey)
{
    this._apiSecretKey = apiSecretKey;

    _httpClient = new HttpClient();
    _httpClient.DefaultRequestHeaders.Accept
        .Add(new MediaTypeWithQualityHeaderValue("application/json"));

    var authInfo = _apiSecretKey;
    authInfo = Convert.ToBase64String(System.Text.ASCIIEncoding.ASCII.GetBytes(string.Format("{0}:", _apiSecretKey)));

    // The two line below because I saw in an answer on stackoverflow.
    _httpClient.DefaultRequestHeaders.Add("Connection", "Keep-Alive");
    _httpClient.DefaultRequestHeaders.Add("Keep-Alive", "3600");

    _httpClient.DefaultRequestHeaders.UserAgent.ParseAdd("Anything.com custom client v1.0");
    _httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Basic", authInfo);

}

以及我发布数据的方法:

And the method where I'm posting the data:

public string CreateHostedPageTransaction(HostedPageRequest req)
{
    var settings = new JsonSerializerSettings { NullValueHandling = NullValueHandling.Ignore };

    // I send this same json content on PostMan and it works. The json is not the problem
    var content = new StringContent(JsonConvert.SerializeObject(req, settings), Encoding.UTF8, "application/json");
    var response = _httpClient.PostAsync(this._baseUrl + "/transactions/hosted", content).Result;
    var responseText = response.Content.ReadAsStringAsync().GetAwaiter().GetResult();

    if (response.IsSuccessStatusCode)
        return responseText;

    return "";
}

然后我在PostAsync行收到此错误:An existing connection was forcibly closed by the remote host.这是错误的详细信息:

Then I get this error: An existing connection was forcibly closed by the remote host, at the PostAsync line. This is the error details:

[SocketException (0x2746): An existing connection was forcibly closed by the remote host]
   System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult) +8192811
   System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) +47

[IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.]
   System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) +294
   System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) +149

[WebException: The underlying connection was closed: An unexpected error occurred on a send.]
   System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context) +324
   System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar) +137

[HttpRequestException: An error occurred while sending the request.]

我正在使用C#4.5，Asp.Net MVC.我一直在阅读相同错误的答案，到目前为止，它们都没有解决我的问题.我在这段代码中缺少什么?

I'm using C# 4.5, Asp.Net MVC. I've been reading answers for the same error and none of them solved my issue so far. What am I missing in this code?

感谢您的帮助

推荐答案

我在您的代码示例中没有看到您正在设置_baseUrl的值，但是我假设这是在某处完成的.我还假设由于这与付款有关，因此URL是HTTPS.如果远程主机禁用了TLS 1.0，并且您的连接以TLS 1.0的身份进入，则可能会导致该行为.我知道C#4.6默认情况下启用了TLS 1.0/1.1/1.2支持，但是我认为C#4.6即使支持TLS 1.1和1.2，仍然默认仅支持SSL3/TLS 1.0.如果这是导致此问题的原因，则可以使用以下代码将TLS 1.1和1.2手动添加到启用的值.

I don't see in your code sample where you are setting the value of _baseUrl, but I'm assuming that is being done somewhere. I'm also assuming that since this related to payments, the URL is HTTPS. If the remote host has disabled TLS 1.0 and your connection is coming in as TLS 1.0, it could cause that behavior. I know C# 4.6 has TLS 1.0/1.1/1.2 support enabled by default, but I think C# 4.6 still defaults to only SSL3/TLS 1.0 even though TLS 1.1 and 1.2 are supported. If this is the cause of the issue, you can manually add TLS 1.1 and 1.2 to the enabled values using the following code.

System.Net.ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;

这篇关于C#HttpClient远程主机强行关闭了现有连接的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！