Comment 6 for bug 1639691

@Clay:

Yes, that's for an account and that's why I separated the reput_objects function as callable with for each account.

For another thought, I found an issue for the reputter scripts. That works *basically* for stored objects but I found a type of object deosn't. That is a delete marker in versioned write history mode including ';' in the content-type. That results in 400 bad request for re-putting.

I pushed a solution for that as separated patch, here https://review.openstack.org/#/c/396603/

However, I'm not sure right now, if swift has another middleware to make such a content-type which can not be re-put-able. If it's only a delete-maker, it's ok to skip them because it should be 0-byte object which is not necessary to re-decode/encode.