Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-727

openstack-swift provider's BlobRequestSigner.signPutBlob does not set payload and content length

    XMLWordPrintableJSON

    Details

      Description

      The BlobRequestSigner.signPutBlob method in the new "openstack-swift" provider does seem to set the payload and content length. Callers have to explicitly set these on the returned HttpRequest object.

      This is different from at least the "swift-keystone" provider.

      HttpRequest returned by the with the "swift-keystone" provider:

      Signed put request: {method=PUT, endpoint=http://10.50.23.43:8080/v1/AUTH_abcd/cloud-testing/erwe?temp_url_sig=6418a27f151ce00e044d798e2908bccd8ba9d3ab&temp_url_expires=1411433648, headers=

      {Expect=[100-continue], ETag=[9c48f2a4023ba27471a8fa259a000fa4, 9c48f2a4023ba27471a8fa259a000fa4], Content-Type=[application/octet-stream]}

      , payload=[content=true, contentMetadata=[contentDisposition=null, contentEncoding=null, contentLanguage=null, contentLength=null, contentMD5=null, contentType=application/unknown, expires=null], written=false]}

      HttpRequest returned by the new openstack-swift provider:

      Signed put request : {method=PUT, endpoint=https://storage101.iad3.clouddrive.com/ v1/MossoCloudFS_asd/cloud-testing/sfsdfsd?temp_url_sig=99c9676a1c ef33ba408b6e35082a056f11a7d717&temp_url_expires=1411454235, headers={}}

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              shrinand Shri Javadekar
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: