2012 R2 .net core http/2

Question

2012 R2 .net core http/2

光陈 1

System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it. System.Net.Http.HttpRequestException No connection could be made because the target machine actively refused it. System.AggregateException One or more errors occurred. (No connection could be made because the target machine actively refused it.) 在windows 2012 中使用HttpClient 调用apple APNs http/2 api 出现异常,求高手帮助 (The SSL connection could not be established, see inner exception.

1 answer

Your answer

Answer 1

Michael Taylor 60,161

This is a standard SSL issue. You are unable to connect to the remote machine. Unfortunately you provide no information on what you were doing, any code involved, whether this was client or server side, what SSL protocols you were using, etc so we aren't going to be much help at this point.

Note the following:

HTTP/2 is not supported on Server 2012 R2. The earliest supported server is 2016 and Windows 10. However there are many clients that don't support HTTP/2 either so at this time web servers generally support HTTP and HTTP/2 to handle either protocol.
TLS 1.2+ is the only recommended protocols for HTTPS. This protocol must be enabled on the client and server in order for them to communicate. The error you're giving tends to indicate that the client and server are not agreeing on this. Refer to the IIScrypto tool for information on how to enable on the server.
You mention .NET Core so that will support TLS 1.2 automatically but older clients like .NET Framework 4.6 apps have to opt into the newer protocol. There is an entire article in MSDN on how to do this.

光陈 1 Reputation point

2021-03-15T15:20:32.663+00:00

我的是一个客户端(client)

光陈 1

        var req = new HttpRequestMessage(HttpMethod.Post, url);
        req.Version = new Version(2, 0);
        req.Headers.Add("apns-priority", push.Priority.ToString());
        req.Headers.Add("apns-push-type", push.Type.ToString().ToLowerInvariant());
        req.Headers.Add("apns-topic", GetTopic(push.Type));
            req.Headers.Authorization = new AuthenticationHeaderValue("bearer", GetOrGenerateJwt());
      req.Headers.Add("apns-expiration", "0");
        if (!string.IsNullOrEmpty(push.CollapseId))
            req.Headers.Add("apns-collapse-id", push.CollapseId);
        req.Content = new JsonContent(payload);
        var resp = await _http.SendAsync(req, ct).ConfigureAwait(false);
        var respContent = await resp.Content.ReadAsStringAsync().ConfigureAwait(false);

Michael Taylor 60,161 Reputation points

2021-03-15T15:43:31.293+00:00

The error indicates you're trying to connect to Apple. They undoubtedly require TLS 1.2. Ensure you have configured your app to use TLS 1.2. That depends upon the platform version you're using (.NET Framework 4.7.2, .NET Core 3.1, etc). Please post that information. Additionally consider using Fiddler or wireshark to capture the packets and confirm that you are sending HTTP/2 packets and the SSL protocols agree. Otherwise you'll get this error.

Given the error, even with SSL, I'm thinking your URL isn't actually valid. Try using Postman to post the same request to the same URL and see what you get back. If you get the same error it is your URL and API endpoint and not the code.
光陈 1 Reputation point

2021-03-15T17:23:33.023+00:00

.NET Core 3.1 + 2012 R2

在net core 3.1 +2019 上已经确认过地址是正确的,是可以建立链接并发送请求的.

具体请求方式与地址都是在:https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns

下面是wireshark 的截图.
Michael Taylor 60,161 Reputation points

2021-03-15T17:55:45.657+00:00

What you posted doesn't display properly. Please post what platform your client code that you posted is using. Please also report the results of using Postman to connect to the same endpoint and URL that you are having an issue with.

If you want to use Fiddler/wireshark then please post the connection information it shows for the request going to the remote endpoint.

Share via

2012 R2 .net core http/2

1 answer

Your answer