ColdFusion 9.0.0 TLSv1.2 [英] ColdFusion 9.0.0 TLSv1.2

问题描述

我正在运行ColdFusion 9.0修补程序3。我正在尝试获取TLSv1.2以用于cf_http标签。我先升级到Java 7 Update 80，然后再升级到Java 8 Update25。使用Wireshark似乎仍在尝试TLSv1.0进行连接，而端点将仅采用TLSv1.2。 TLSv1.2，但似乎不是让Cold Fusion使用它的方法。有什么想法吗？

I am running ColdFusion 9.0 Hotfix 3. I am trying to get a TLSv1.2 to work for cf_http tag. I started with an upgrade to Java 7 Update 80 and then Java 8 Update 25. Using Wireshark it looks like it is still connecting trying TLSv1.0 and the end point will only take TLSv1.2 From what I have read Java 7 and 8 support TLSv1.2, but doesn't seem to be a way to get Cold Fusion to use it. Any ideas?

Windows 2008 32bit

Windows 2008 32bit

在侧面，我知道版本9很旧并且正在工作有关升级到新版本的问题，但是这部分内容需要解决，我们计划完成升级，并且测试和升级会破坏某些站点。

On a side note I know version 9 is old and I am working on upgrading to a new version, but this part came up and needs to be done before we planned to finish the upgrade and testing and upgrading breaks some of the site.

推荐答案

我已经写了两年的博客了；自Authorize.net& PayPal宣布SSL升级与ColdFusion 8& amp;不兼容。 9.我的解决方法是使用Adiabata，Inc.的 CFX_HTTP5 。Windows C ++标记修复了ColdFusion 3-11中所有与ColdFusion相关的错误。它建立在WinHttp 5.1 API（本机Windows HTTP层）上，因此支持所有安全和身份验证协议，无论ColdFusion是否支持它们。它还更快，并支持多达64个并发/异步请求和客户端证书。如果您访问的服务器最近更改了IP，它将使用DNS TTL，并且不需要重新启动。 （CFHTTP DNS缓存是从不或永远。）

I've been blogging about this for a couple years; ever since Authorize.net & PayPal announced SSL upgrades that weren't compatible w/ColdFusion 8 & 9. My workaround has been to use CFX_HTTP5 from Adiabata, Inc. This Windows C++ tag fixes all ColdFusion-related bugs in ColdFusion 3-11. It's "built on WinHttp 5.1 API - native Windows HTTP layer - and, therefore, supports all security and authentication protocols, regardless of whether ColdFusion supports them or not." It also faster and supports up to 64 concurrent/asynchronous requests and client-side certificates. It honors DNS TTL and doesn't require a reboot if a server you access has recently changed IPs. (CFHTTP DNS caching is either "never" or "forever".)

我建议使用CFX_HTTP5的其他原因是：1）有效，2）提供了更多连接/请求选项； 3）确保在所有版本的ColdFusion上都具有一致的功能和行为； EOL和未来。

The other reasons I recommend using CFX_HTTP5 is that it 1) works, 2) provides more connection/request options and 3) ensures consistent functionality and behavior across all versions of ColdFusion; EOL and future.

这是一个非常基本的示例：

Here's a very basic sample:

<CFX_HTTP5 METHOD="POST"
    URL="https://apitest.authorize.net/xml/v1/request.api"
    HEADERS="Content-Type: text/xml#Chr(13)##Chr(10)#"
    BODY="#xmlString#"
    OUT="RESULT">

<CFIF STATUS NEQ "OK">
    <CFTHROW MESSAGE="#ERRN# #MSG#">
</CFIF>

<CFSET returnedXML = RESULT>

这篇关于ColdFusion 9.0.0 TLSv1.2的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！