On 5/24/2012 4:29 PM, Greg wrote:
It is mostly the likely the self-signed certificate issue you suspected. Java (and other languages) are pretty notorious for rejecting such unless you configure them just right. I haven't worked with Java in 10 years, so my knowledge of how to fix that is pretty useless, hopefully another will speak up and help. You probably had to use -k with curl right? That would confirm the self-signed issue.
I was using the curl command from the howto, I can confirm that it has -k.
Just as a note, the SSL capabilities for the Swift proxy server are truly for basic testing only. You might want to start with non-SSL and then lock it down after you get things working otherwise.
It took a few tries to figure out everything, but I finally got it working with SSL turned off. I will look at an SSL terminating load balancer for production.
Thanks, Shawn _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
