Comment 3 for bug 1509429

Perhaps the best way to fix this is to update the Swift API under openstack-api-site to match the implemented behaviour.
I would raise the importance to Medium, I always get nervous when behaviour does not match the API. Makes me suspicious of the entire API. We should also add some tests to catch when behaviour does not match the published API.

I was going to use the X-Timestamp in the COPY response as part of tiering middleware.
I was going to use this X-Timestamp to force the timestamp of the symlink created after the copy to the cold-tier.
Clay, you discussed this timestamp manipulation in the tiering spec as a way to close a window of vulnerability between the COPY and the symlink creation.

I don't absolutely need the X-Timestamp from the COPY response, but it would be nice.
As an alternative, I can have the tiering middleware generate a timestamp, and force both the copied object and the symlink to
both use this middleware-generated timestamp.