This PR fixes the case where jclouds is assuming the blob content type to be `application/unknown`. The original discussion can be found [here](http://markmail.org/thread/qdxqrkhnjygjny4k).
If the user does not specify a content type, then the `X-Detect-Conent-Type` header should be added to the request headers to indicate that the server should detect the content type. This feature is supported in the Swift 1.9.1 through 1.13.1rc1 [releases](https://bugs.launchpad.net/openstack-api-site/+bug/1274988). A test case is in the works now and I wanted to get some other eyes on it. DO NOT MERGE. You can merge this Pull Request by running: git pull https://github.com/rackspace/jclouds fix-swift-content-type Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/338 -- Commit Summary -- * Allow Swift to set content type -- File Changes -- M apis/swift/src/main/java/org/jclouds/openstack/swift/blobstore/functions/BlobToObject.java (11) M apis/swift/src/main/java/org/jclouds/openstack/swift/reference/SwiftHeaders.java (3) -- Patch Links -- https://github.com/jclouds/jclouds/pull/338.patch https://github.com/jclouds/jclouds/pull/338.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/338
