在调用UPS跟踪REST服务的API时，出现“由于远程方关闭了传输流，认证失败”的错误。

Question

我正在将 UPS 跟踪 API 实现到我的 asp.net mvc 5 应用程序中。我创建了以下方法：

public virtual Core.UPSTrackingResponse.UPSTrackingResponse TrackUPS(string trackingNumber)
{
    Core.UPSTrackingRequest.UPSTrackingRequest requestModal = new Core.UPSTrackingRequest.UPSTrackingRequest();
    requestModal.UPSSecurity.ServiceAccessToken.AccessLicenseNumber = UPSAccessKey;
    requestModal.UPSSecurity.UsernameToken.Username = UPSUserId;
    requestModal.UPSSecurity.UsernameToken.Password = UPSPassword;
    requestModal.TrackRequest.InquiryNumber = trackingNumber;
    requestModal.TrackRequest.Request.RequestOption = "1";
    requestModal.TrackRequest.Request.TransactionReference.CustomerContext = trackingNumber + " tracking context";

    string Data = new JavaScriptSerializer().Serialize(requestModal);
    string response = "";
    System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3 | SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;
    HttpWebRequest request = (HttpWebRequest)WebRequest.Create(UPSTrackingURL); // https://wwwcie.ups.com/rest/Track
    request.Method = "POST";
    request.KeepAlive = false;
    request.ProtocolVersion = HttpVersion.Version10;

    request.ContentType = @"application/json";
    request.ContentLength = Data.Length;

    StreamWriter requestWriter = new StreamWriter(request.GetRequestStream(), System.Text.Encoding.ASCII);
    requestWriter.Write(Data);
    requestWriter.Close();

    try
    {
        WebResponse webResponse = request.GetResponse();
        Stream webStream = webResponse.GetResponseStream();
        StreamReader responseReader = new StreamReader(webStream);
        response = responseReader.ReadToEnd();
        Console.Out.WriteLine(response);
        responseReader.Close();
        Nop.Core.UPSTrackingResponse.UPSTrackingResponse ResponseModal =
            new JavaScriptSerializer().Deserialize<Nop.Core.UPSTrackingResponse.UPSTrackingResponse>(response);
        return ResponseModal;
    }
    catch (Exception ex)
    {
        return null;
    }
}

我在本地机器上调用此代码时运行正常。但是当我将应用程序部署到AWS服务器上时，它一直给我以下异常。可能的原因是什么？我现在卡住了。

System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   at System.Net.HttpWebRequest.GetRequestStream()
   at Nop.Services.Shipping.ShippingService.TrackUPS(String trackingNumber)
   at Nop.Web.Controllers.OrderController.PrepareShipmentDetailsModel(Shipment shipment)
   at Nop.Web.Controllers.OrderController.ShipmentDetails(Int32 shipmentId)
   at lambda_method(Closure , ControllerBase , Object[] )
   at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<BeginInvokeSynchronousActionMethod>b__39(IAsyncResult asyncResult, ActionInvocation innerInvokeState)
   at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`2.CallEndDelegate(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3d()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>c__DisplayClass46.<InvokeActionMethodFilterAsynchronouslyRecursive>b__3f()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass33.<BeginInvokeActionMethodWithFilters>b__32(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<>c__DisplayClass2b.<BeginInvokeAction>b__1c()
   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass21.<BeginInvokeAction>b__1e(IAsyncResult asyncResult)
   at System.Web.Mvc.Controller.<BeginExecuteCore>b__1d(IAsyncResult asyncResult, ExecuteCoreState innerState)
   at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult)
   at System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult)
   at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult)
   at System.Web.Mvc.MvcHandler.<BeginProcessRequest>b__5(IAsyncResult asyncResult, ProcessRequestState innerState)
   at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult)
   at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

- Jitendra Pancholi

---

那台AWS服务器和你的本地机器上安装了哪个.NET框架版本？ - Evk

你可能需要证书认证。 - Amorphis

你是否使用的访问密钥仅适用于本地开发机器（localhost: ***），但是当它部署到服务器并且域名更改时，该访问密钥对于请求客户端无效？ - Gurpreet

@Evk：本地和服务器都已安装了.NET 4.5.2框架。 - Jitendra Pancholi

@Gurpreet：不，本地或服务器没有单独的密钥。 - Jitendra Pancholi

Answer 1

在调用 Web 服务之前，在代码的某处添加以下内容：

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

- Alex K

---

这对我解决了问题。 - brendonparker

这个程序只在我的本地IIS上运行正常，但是在AWS上部署后就无法工作。 - Jitendra Pancholi

Answer 2

如果您使用的是.NET 4.0或.NET 3.5，那么Alex K的答案将无法帮助您。 解决此问题的最佳方法是升级.NET。

如果无法升级： 对于.Net 4.0，请使用以下代码：

ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;

还有一个注册表hack，可以强制4.5默认使用TLS 1.2而不需要在程序中强制执行。

对于.NET 3.5：

现在有一个可用的补丁程序，为.NET 3.5提供了TLS1.2支持。

更多细节请参见此处来源： https://blogs.perficient.com/2016/04/28/tsl-1-2-and-net-support/

- Proggear