Nevermind - egg on face. There was an exception caught in my code, but it was
buried in the middle of the HttpResponseException content so I missed it. The
problem turned out to be one where s3 ninja was literally returning success
without having written the file due to a previous error where
On Fri, Aug 17, 2018 at 10:04:29PM -, john.calc...@gmail.com wrote:
> I'm calling putBlob to put a blob to an S3 ninja server. The server is
> returning a ridiculous 500 server error response page - it contains a ton of
> javascript and the jclouds SAX parser is choking on the content of a
I'm calling putBlob to put a blob to an S3 ninja server. The server is
returning a ridiculous 500 server error response page - it contains a ton of
javascript and the jclouds SAX parser is choking on the content of a
