Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-18 Thread Brian FitzGerald
If you use a centralised storage for all servers in your cluster then it is easy. Russ, thanks a lot for your response (somehow I missed it last week). I read the article you linked to about client variables (good read). Are you aware of any resources which discuss how one might implement a

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-18 Thread Russ Michaels
I did it once long ago when I was still a developer, it was probably on CF5 or 6. I will presume Windows is used here, if not, just translate tot he Unix equivalents. It is basically just a file server, network attached storage, a SAN or whatever you have available. You MAP a drive on your web

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-15 Thread Brian FitzGerald
Hey Dave, Thanks a lot for your response. Please see some comments inline below: Are you using clustering to support a larger number of users than a single server? Or are you using it to provide failover in case a server fails? Or both? The clustering is mainly for supporting a large number

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-15 Thread Dave Watts
I'm hoping it's the former :) I guess that's what I'm getting at though... I'm sure you've done many applications that run on clustered servers, is using sticky sessions a common and accepted practice for using cfcs in a clustered environment? Or do larger applications like this just

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-15 Thread Russ Michaels
If you use a centralised storage for all servers in your cluster then it is easy. You save session data to your san disk. And simply reload it if it gets lost due to switching servers. You can also achieve this with replication between local disks too. Remember the session is stored in a cookie

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-15 Thread Brian FitzGerald
Lots of people use sticky sessions to solve this problem. That doesn't provide failover, but if you're not doing something extremely critical where the user can just go elsewhere (ex: ecommerce) you might not need failover. With sticky sessions, in the event that one server crashed, the users on

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2013-11-15 Thread Dave Watts
Lots of people use sticky sessions to solve this problem. That doesn't provide failover, but if you're not doing something extremely critical where the user can just go elsewhere (ex: ecommerce) you might not need failover. With sticky sessions, in the event that one server crashed, the

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2011-06-17 Thread Brian FitzGerald
You'll need to download the certificate and install it in your JVM's keystore. Google java keystore keytool coldfusion for instructions. Hi Dave, Thank you for the reply. Only thing is that I've already downloaded the certificate through Google Chrome, and imported it via the keytool as

RE: cfhttp and SSL ... I/O Exception: peer not authenticated

2011-06-17 Thread Bobby Hartsfield
I'm pretty sure it's related to the fact that I'm trying to make a secure request (SSL), and maybe since I'm on my local development machine and thus don't have a local SSL setup on my end as well it's causing problems (maybe?). Yes, most likely. If you have a self signed cert, you can add it to

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2011-06-17 Thread Brian FitzGerald
Hey Bobby, thanks for the reply. It turns out this is a CF9 bug. Ray Camden outlines it well here, with a workaround that is working for me: http://www.coldfusionjedi.com/index.cfm/2011/1/12/Diagnosing-a-CFHTTP-issue--peer-not-authenticated Here is the bug report Jason Dean filed:

Re: cfhttp and SSL ... I/O Exception: peer not authenticated

2011-06-16 Thread Dave Watts
I'm trying to make a cfhttp call to a secure url (the API for http://spreedly.com) and this is what I keep getting back: ErrorDetail      I/O Exception: peer not authenticated Filecontent      Connection Failure Mimetype         Unable to determine MIME type of file. Statuscode