> + * uploaded object.
> + */
> + private class BlobUploader implements Callable<BlobDetail> {
> + private String container;
> + private BlobDetail toBeUploadedBlobDetail;
> +
> + protected BlobUploader(String container, BlobDetail
> toBeUploadedBlobDetail) {
> + this.container = container;
> + this.toBeUploadedBlobDetail = toBeUploadedBlobDetail;
> + }
> +
> + @Override
> + public BlobDetail call() throws Exception {
> + Blob blob =
> storage.blobBuilder(toBeUploadedBlobDetail.getRemoteBlobName())
> + .payload(toBeUploadedBlobDetail.getLocalFile())
> + .contentType("")
Cloud Files will set the content type of the file itself if you pass it an
empty Content-Type header. If you don't do that then jclouds sends Content
Type: application/unknown and Cloud Files can get confused. But I was doing
some testing and it appears it may not be necessary. I'll leave it off for now
and we'll see what happens.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/11/files#r5438996
