On Wed, Jun 19, 2013 at 8:21 AM, Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx> wrote: > Yehuda, > > Thanks for your reply. Is this not a bit un-Swift like? I came across > this while testing the backup service for Openstack Cinder. Cinder > currently supports backup to Swift so I tested this against Rados > Gateway but it does not work because the it uses the standard > http://<server>/<version>/<account> format. The url should not be built directly, but rather use the returned storage-url that it got when authenticated with the auth service. Swift happens to build it in that format. > > Also, there is an issue with PUTs where RGW returns a "411 Length > Required" in case the content-length is not specified. Is content-length > mandatory? Swift does not seem to complain. What are your thoughts on this? > A PUT without content length needs to be chunked. If the missing content-length is missing, we require 'Transfer-Encoding: chunked'. > (updated the subject since it was wrong) > > Ed. > > On 19/06/13 16:08, Yehuda Sadeh wrote: >> On Wed, Jun 19, 2013 at 3:03 AM, Edward Hope-Morley >> <opentastic@xxxxxxxxx> wrote: >>> Apologies, premature send ;) >>> >>> On 19/06/13 11:00, Edward Hope-Morley wrote: >>>> Hi guys, I'm having the following issue with the RGW swift API: >>>> >>>> The docs at http://ceph.com/docs/next/radosgw/swift/serviceops say that >>>> for a GET request to list account contents I should do (as with Swift): >>>> >>>> GET /{api version}/{account} HTTP/1.1 >>>> >>>> >>>> but, if I put the account RGW treats this as a bucket. >>>> >>>> So the following works fine: >>>> >>>> curl -i http://192.168.1.201:80/swift/v1 -X GET -H "X-Auth-Token: $token" >>>> >>>> But this does not: >>> curl -i http://192.168.1.201:80/swift/v1/$account -X GET -H >>> "X-Auth-Token: $token" >>> >>> Am I doing something wrong or is this an anomaly in the RGW API? >>> >> The docs are wrong there, the account is determined by the auth token. >> >> Yehuda > -- 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
