CODEWITHSUNDEEP
coldfusion
user804401
user804401

Reputation: 1994

Connect to web service error Connection Failure: Status code unavailable:

We are making a cfhttp call to connect to an https web service. We are getting the this error:

Connection Failure: Status code unavailable

I searched Google but have found no solutions.

From the production server I am able to hit the web service URL.

I am a .Net developer and I am not sure of this technology.

Any pointers will be helpful.

Here is the line of code we are using to make the connection:

<cfhttp url="#arguments.TheIP#" method="post" throwonerror="true" timeout="45">
    <cfhttpparam type="header" name="SOAPACTION" value="#arguments.TheHeader#">
    <cfhttpparam type="XML" value="#arguments.TheXML#">
</cfhttp>

Upvotes: 0

Views: 6438

Answers (4)

Zulfiqar Ali
Zulfiqar Ali

Reputation: 123

Make sure your cfhttp link is correct. I face this issue and it totally based on incorrect cfhttp link.

Upvotes: 0

Jas Panesar
Jas Panesar

Reputation: 6639

I have faced / solved this a few times, the snippet below hopefully will work for you. I highly recommend learning about it in stead of simply trying it.

I place this in my Application.cfc, but you could put it right in your script right before the cfhttp call as well.

<!--- fix for HTTPS connection failures --->
<cfif NOT isDefined("Application.sslfix")>
    <cfset objSecurity = createObject("java", "java.security.Security") />
    <cfset objSecurity.removeProvider("JsafeJCE") />
    <cfset Application.sslfix = true />
</cfif>enter code here

Upvotes: 2

williambq
williambq

Reputation: 1125

Hum... First thing that appears odd is your IP argument as mentioned by barnyr. The response you are getting makes me think you are getting NO response at all (the request is completely ignored, not just erring). So some setting is causing them to ignore your request.

As of CF9 I use cfscript to do this kind of thing via HTTP when I can't use regular webservice java object proxy stubs.

Here is a working SOAP call via http() (because of .net to cf inability to communicate complex object hash maps via regular soap I resorted to this, among other things).

This is a cf to .net service call so it might be relevant for you as they are using just the built in tools to gen their SOAP service which was not perfectly Axis 1 SOAP happy-go-lucky. In particular I had to play with some of the extra settings and headers to get it just so and specifically add the soap action into a header (which is usually derived from the SOAP body envelope).

Additionally, I am using oasis security which I had to stuff inside the envelope/body.

Here is the code (inside a cfc) that you might try updated as you need:

        //////////////////////////////////////////////////////////////////////////
        // BUILD HTTP REQUEST
        //////////////////////////////////////////////////////////////////////////
        Local['SoapAction'] = "XYZ.Commercial.Mapping.ServiceContracts/IService/#Arguments.szMethodName#"; // THIS IS CASE SENSITIVE
        var oH = new Http();
        oH.setMethod('post');
        oH.setCharset('utf-8');
        oH.setUserAgent('Axis/1.2.1');
        oH.setTimeout(30);
        oH.setURL(Arguments.szURL);
        // INCLUDING THE SOAPACTION AS A HEADER IS SPECIFIC TO XYZ - USUALLY THE OPERATION IS DECIPHERED FROM THE ENVELOPE BODY TAGS - XYS REQUIRES THIS PATHING TO MATCH FOR THE SOAP ACTION HEADER VALUE
        oH.addParam(type="HEADER", name="SOAPAction", value='#Local.SoapAction#'); 
        oH.addParam(type="HEADER", name="Content-Type", value='text/xml');
        oH.addParam(type="body", value=Arguments.szBody);
        ///////////////////////////////////////////////////////////////////////////

        /////////////////////////////////////////////////////////////////////////////
        // EXECUTE HTTP
        Local['rsHttpSend']= oH.send();
        // SET RESULTS
        Local.nStatusCode = val(Local.rsHttpSend.getPrefix().StatusCode);
        Local.szResponse = Local.rsHttpSend.getPrefix().FileContent;
        Local.szHeader = Local.rsHttpSend.getPrefix().Header;
        /////////////////////////////////////////////////////////////////////////////////////////////////////////////////

This approach was coupled with using SoapUI to verify the final soap body post was valid. So if you can do that too, you should be able to use this vector.

Let me know if you get any farther.

Upvotes: 1

barnyr
barnyr

Reputation: 5678

Here are a list of things to check:

  • The variable for the URL is TheIP. Make sure this actually a properly formatted URL, not just a URL.

  • Check that the target server's certificate is installed in the JVM's trust store. in Windows and I think .Net, the system's own certificate store is used, so if your browser can get to the URL you're ok. In Java there is a file which contains a list of Trusted Certs. Instructions on importing those certs are in the CF docs for CFHTTP.

  • Check the ColdFusion logs for evidence of failure. c:\coldfusion9\logs\exception.log is probably a good place to start.

Upvotes: 0

Related Questions