cfml

my CFHTTP issue is back. Hitting <http://smarty.com|smarty.com> from cftry works but doesn't work from my server.

[SOLVED]: Tell jvm to use specific TLS version -Dhttps.protocols=TLSv1.2.  <http://smarty.com|smarty.com> only accepts 1.2 or 1.3.

Its not a TLS issue. <http://Smarty.com|Smarty.com> supports 1.2 and 1.3 and my server only uses 1.2.

The output of cfhttp.filecontent is "Connection Failure"

If I use the browser on the same server and hit <http://smarty.com|smarty.com> directly it works. So it can't be network related.

Smarty api doesn't have any "Allowed Hosts" list where I have to add my website or IP. Its perfectly fine to use the same URL request from anywhere (ofcourse it needs my auth info).

need to verify the version CF is running on is using the proper TLS (aka 1.2)

CF 2018 and java 11.0.1 2018-10-16 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)

this is a Enterprise ACF 2018 Gui install

Take a look here: <https://www.petefreitag.com/item/916.cfm>

So my verison of JRE 11.0.1 is probably using TLSv1 or TLSv1.1????

No, your version should be using 1.2 I believe

How does this work? I use windows server and IIS and in the windows registry I disable a bunch "weak" protocols and ciphers using IISCrypto.

This is all that I have enabled on my server?

Thanks chiming in Patrick.

<@U0BJHDX1Q> I emailed <mailto:cf.install@adobe.com|cf.install@adobe.com> - hopefully I can get this fixed asap.

FWIW, it also works locally from my commandbox servers.

Yea this is def a config issue on your actual server if its working otherwise

Can't be a CF Admin config setting because I have exported those and imported those to my commandbox servers.

Do you mean installation files config?

Basically it seems that your windows server or java is configured to use 1.1 or a non-supported call method thus the 3rd party api is crapping out

<@U0PNJPC31> also I believe in CFAdmin you can add jvm params; try adding this: `-Dhttps.protocols=TLSv1.2`

I will try this and restart server tonight