cfhttp uknown host, uknown error

62 views
Skip to first unread message

Brian FitzGerald

unread,
Jun 27, 2016, 8:57:09 PM6/27/16
to Lucee
Hey guys, I'm trying to interact with the IBM Watson API from Lucee 4 and am running into a problem with <cfhttp>.

Here is the code:

<cfhttp
 
url="https://stream.watsonplatform.net/text-to-speech/api/v1/synthesize?text=hello%20world"
 
method="get">

 
<cfhttpparam type="header" name="Authorization" value="Basic #ToBase64("myusername:mypassword")#">

</cfhttp>


<cfdump var="#cfhttp#"><cfabort>

I can get a response via curl and via the browser (after I authenticate) Any thoughts on how to best troubleshoot this?

Thanks,
Brian

Julian Halliwell

unread,
Jun 28, 2016, 3:59:52 AM6/28/16
to lu...@googlegroups.com
What JRE version are you using? If Java 7 then try upgrading to 8. 


--
Win a ticket to dev.objective from Lucee via Twitter, see http://bit.ly/1UbTMWj for details, good luck and see you there...
---
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/6c4b4ce5-48ec-45da-97d2-c304f702db16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Brian FitzGerald

unread,
Jun 28, 2016, 9:50:15 PM6/28/16
to Lucee
Thanks Julian,

I am using the Lucee4 docker image and was able to get this resolved thanks to the help of Joe Gooch and Geoff Bowers. I don't know how to explain it particularly well, but basically it turned out the cacerts in Lucee needed to be updated with the cacerts from the Java runtime on the host operating system, as the Lucee cacerts are a bit out of date (or something).

For future users of the Lucee Docker images, the good news is that it looks like Joe and Geoff are working together to get this patch into the base Lucee Docker images so future users (at least those using the Docker images) won't run into it.

Anyhow, thanks again Joe, Geoff and Julian!
Brian
Reply all
Reply to author
Forward
0 new messages