Been using Worldpay for years to send credit card charges in using cfthttp.

Suddenly, two weeks ago, Worldpay server produced a connection failure.  Told by them to update the URL to something different.New.

Did that, and it worked again ... 5 days later it stopped working again, same error.

This time they (Worldpay) blame it on a firewall issue at our ISP ... rubbish.  Had firewall disabled temporarily.  But WPay admit they have updated their SSL certificates.

We find that while ColdFusion sends URL and gets connection failure, when we use the same URL in a BROWSER on any server in our ISP or anywhere else globally, it works ... we get a "proper" error message from their server (invalid account) but not a connection failure.

So "drastic" is this failure, that when we add parameters timeout="5"  and throwonerror="Yes" to the CFHTTP routine (should be there anyway, I know) we get a CF error ..

Connection Failure: Status code unavailable.

Environment:

Windows: 2000 Advanced Server .. NO comemnts please on client upgrade path!  It works.

IIS:   6?

CF:  8

But we have tested this on 3 different servers ... running CF 7 also and other Win O/S.

Is there somewhere in the CF7, CF8 admin panel where we do something to update the SSL certificate for this vendor?

We ran wireshark on the server to see if perhaps CF had been corrupting the http URL string and that Worldpay would work before but now is less tolerant of a "corrupt" string but it looks fine.