Content-disposition not copying

I’m copying between Rackspace and S3. The content-disposition header is important to us for hosting. I see it in the dumped headers, but it does not copy to S3. Is there a way to do this? Debug log below.

2018/03/14 05:52:54 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2018/03/14 05:52:54 DEBUG : <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2018/03/14 05:52:54 DEBUG : HTTP RESPONSE (req 0xc420baa500)
2018/03/14 05:52:54 DEBUG : HTTP/1.1 200 OK
Content-Length: 609605
Accept-Ranges: bytes
Content-Disposition: inline; filename=“Green and Blue Day Layout.pdf”
Content-Type: application/pdf
Date: Wed, 14 Mar 2018 12:52:54 GMT
Etag: *************
Last-Modified: Tue, 14 Jan 2014 11:05:18 GMT
X-Timestamp: 1389697517.38931
X-Trans-Id: ************-005aa91b26dfw1

2018/03/14 05:52:54 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018/03/14 05:52:55 DEBUG : >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2018/03/14 05:52:55 DEBUG : HTTP REQUEST (req 0xc420a7a200)
2018/03/14 05:52:55 DEBUG : PUT /************************/Green_and_Blue_Day_Layout.pdf HTTP/1.1
Host: s3-us-west-1.amazonaws.com
User-Agent: rclone/v1.39
Content-Length: 609605
Authorization: XXXX
Content-Type: application/pdf
X-Amz-Acl: public-read
X-Amz-Content-Sha256: *********
X-Amz-Date: 20180314T125255Z
X-Amz-Meta-Mtime: 1389697518
Accept-Encoding: gzip

Alas rclone doesn’t preserve this at the moment.

It will preserve the content-type.

I’ve had some ideas on how to do this kind of thing so can you make a new issue on github and I’ll see what we can do!

2 Likes