Diwaker Gupta created JCLOUDS-204:
-------------------------------------

             Summary: S3 multi-part uploads don't honor content-type & 
content-disposition
                 Key: JCLOUDS-204
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-204
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-blobstore
    Affects Versions: 1.6.1
            Reporter: Diwaker Gupta
             Fix For: 1.6.2


Sample headers from a 4KB file uploaded using jclouds:

{noformat}
HTTP/1.1 200 OK
x-amz-id-2: k4MQk9+abyU9SPDs1xM0wuH/aZOAN2XZXEwk70APErzgVZkg1QpSmkJ8uXhnDq5P
x-amz-request-id: F86A27E1D90E3CFD
Date: Wed, 10 Jul 2013 05:20:51 GMT
Content-Disposition: inline; filename=IMG_0000.MOV
Last-Modified: Wed, 10 Jul 2013 05:20:40 GMT
ETag: "620f0b67a91f7f74151bc5be745b7110" 
Accept-Ranges: bytes
Content-Type: video/quicktime
Content-Length: 4096
Server: AmazonS3
{noformat}

Note the content-disposition and content-type flags. Now consider the headers 
from a similarly named 1-GB file uploaded using multi-part upload:

{noformat}
HTTP/1.1 200 OK
x-amz-id-2: Hox2BcBsDrwaNMSohRYM7OKZJdO+6+S2EC78v6hKFKsN/rnKLiaJ337Bd9XY22mb
x-amz-request-id: C693A5FAA0228346
Date: Wed, 10 Jul 2013 05:06:22 GMT
Last-Modified: Tue, 09 Jul 2013 00:28:41 GMT
ETag: "3ea49a0c05da9be44d9915f1bbdb259e-33" 
Accept-Ranges: bytes
Content-Type: binary/octet-stream
Content-Length: 1099199149
Server: AmazonS3
{noformat}

Note the absence of content-type and content-disposition.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to