With a bit of HTTP background I’d say: bytes=0-1000000 means: First byte to to 1000000nd byte. First byte is byte #0 On an empty object there is no first byte, i.e. not satisfiable ==> 416 Should be the same as on a single byte object and bytes=1-1000000 200 OK should only be correct, if the server or a proxy in between doesn’t support range requests. Ciao, Uli > On 21. 03 2022, at 14:47, Kai Stian Olstad <ceph+list@xxxxxxxxxx> wrote: > > Hi > > Ceph v16.2.6. > > Using GET with Range: bytes=0-1000000 it fails with 416 if the object is 0 byte. > I tried reading the http specification[1] on the subject but did not get any wiser unfortunately. > > I did a test with curl and range against a 0 byte file on Nginx and it returned 200 OK. > > Does anyone know it's correct to return 416 on 0 byte object with range or should this be considered a bug in Ceph. > > > [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35.1 > > -- > Kai Stian Olstad > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |