iirc we return 409 in case you're trying to recreate the bucket in a different region. I don't see why we should return it if the user tries to create it in the same region it exists in. Amazon does not return 409 if a bucket is recreated on their main region (where it already exists), so I'm not sure why there should be an inconsistency when dealing with other regions. Yehuda ----- Original Message ----- > From: "Harshal Gupta" <harshal.gupta001@xxxxxxxxx> > To: "ceph-devel" <ceph-devel@xxxxxxxxxxxxxxx> > Sent: Wednesday, June 10, 2015 5:22:51 AM > Subject: Duplicate bucket creation Response in RGW > > Hi, > > I was comparing response of S3 and Ceph RGW for when we try to create > a bucket which already exists for the same account. > > S3 (non-default region) throws an error with: > HTTP response code : 409 Conflict > error code : BucketAlreadyOwnedByYou > > but on the other hand ceph gives a 200 OK while keeping the original > bucket as it is. > > I am thinking to match the functionality of Ceph RGW same as s3 > (non-default regions), as the one given by S3 seems more appropriate. > > For this, I have added a new error code "BucketAlreadyOwnedByYou" > which will be thrown in the above mentioned > case. > > Please give your opinion about it. > > Thanks > > -- > HARSHAL GUPTA > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
