swift client header is not used for uploading large object

[Tong Li]

swift client recently added header command line option, but when large object (segmented) upload occurs, the headers only
used for manifest file not for the segment. This creates inconsistency issues.

The header should be also applied for the segment upload request.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/25319

[Allan Yung (allan-yung)]

This can have serious repercussions with the 'X-Delete-After' header.

The object-expirer will correctly delete manifests with the header, but not the segments, as they do not have the header.

This can lead to accounts filling their quota, when people expect that the large objects are getting expired, rather than just the manifests

[sirkonst (sirkonst)]

Ping.

[Sirisha Guduru (guduru-sirisha)]

Instead of setting the expiration headers on the segments, can we simply delete the segments as well when there is a header set on the manifest? Like it happens when we actually delete a large object using the client.

[Aloïs (maloddon)]

In fact, applying headers on every request might be easier.
This issue still really serious since it might cost a lot to impacted people.

[Eric Rouleau (xblitz)]

Any news on this? the latest python-swiftclient is still impacted by this.

[Valentin Spinnler (vaelu)]

Is there any update on this issue? I mean the X-Delete-After header for example is really useless when the segments don't get deleted then..