I think now that container sync doesn't require the 202 we can consider deprecating compatibility with old container sync agents and returning the 409 directly as the error it is
We should *not* revert the behavior that allowed the proxy to place the object on handoff nodes and return 201 - we should just return the 409 from the object servers that already have the same ts or newer and know that new-ish container-sync will be fine with that (it will right?).
I think now that container sync doesn't require the 202 we can consider deprecating compatibility with old container sync agents and returning the 409 directly as the error it is
https:/ /github. com/openstack/ swift/blob/ a30351bdfc60f82 7979c5afe76ad40 bf3a2b05c3/ swift/proxy/ controllers/ obj.py# L482
We should *not* revert the behavior that allowed the proxy to place the object on handoff nodes and return 201 - we should just return the 409 from the object servers that already have the same ts or newer and know that new-ish container-sync will be fine with that (it will right?).