> Also, have you been able to try Ranjith's suggestion [2] and use the ApacheHC > driver? It is SUCCESS for real. Last time I tried and failed because I mixed with services/Walrus and S3Client. I created a container and verified using s3curl.
Thanks a lot! Julie -----Original Message----- From: Andrew Phillips [mailto:[email protected]] Sent: Sunday, January 31, 2016 1:35 PM To: [email protected] Subject: RE: Use JClouds to talk to non AWS cloud with S3 API Hm...not much difference there: s3curl call that succeeds: HEAD /public HTTP/1.1 User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 Host: jag-itop-svr.dev.opsware.com:8080 Accept: */* Date: Sun, 31 Jan 2016 17:54:30 +0000 Authorization: AWS test:tester:K4fukbjysjqzsArmq8EXHnc/tnE= jclouds call that fails: HEAD http://jag-itop-svr.dev.opsware.com:8080/public HTTP/1.1 Date: Sun, 31 Jan 2016 21:18:50 GMT Authorization: AWS test:tester:jxcGT++8gYPHXO8Vpgt2FtIu9FI= Can you try to reproduce the successful call using 'plain' cURL [1], then without each of the headers that are different ('User-Agent', 'Host' and 'Accept')? Hopefully, that will allow us to figure out which of those three headers is causing the 500. Also, have you been able to try Ranjith's suggestion [2] and use the ApacheHC driver? Regards ap [1] https://curl.haxx.se/ [2] http://markmail.org/message/7gw6wnpbaefgp64r
