copyObject not working when replacing metadata

[NeoPhi]

When trying to use s3.client.copyObject with MetadataDirective: 'REPLACE' I don't see standard metadata headers such as CacheControl or ContentType being included in the request. Additionally the request fails with:

<Error><Code>NotImplemented</Code><Message>A header you provided implies functionality that is not implemented</Message><Header>Transfer-Encoding</Header><RequestId>E45E0F55BA68E46D</RequestId><HostId>...</HostId></Error>

Indicating that the PUT request is including a header I didn't specify causing it to be rejected with a status code of 501. Seems like a variation of: https://forums.aws.amazon.com/message.jspa?messageID=191792

[NeoPhi]

In looking around a little more it looks like in s3.api.js the copyObject definition doesn't specify including all of the headers that a standard putObject request does which should address the first problem I was seeing of metadata not being included.

[NeoPhi]

I was able to work around the Transfer-Encoding issue with this little hack in http.js handleRequest right after the options object is created:

    if ((options.method === 'PUT') && (!request.body)) {
      if (!options.headers) {
        options.headers = {};
      }
      if (!options.headers['Content-Length']) {
        options.headers['Content-Length'] = 0;
      }
    }

This would need to be cleaned up to be a general solution to the problem.

[lsegal]

The above commit should fix the copyObject method failing outright; it does not address the other part of your issue, though (still working on that one).

[trevorrowe]

The missing headers should have been addressed in commit 362ed44. I was able to use the latest (unreleased) code to perform a copy object. This should go out with our next release.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.