[ceph-users] Re: RadosGW S3 range on a 0 byte object gives 416 Range Not Satisfiable

With a bit of HTTP background I’d say: bytes=0-100 means: First byte to to 100nd 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-100 200 OK should only be correct, if the serv

[ceph-users] Re: RadosGW S3 range on a 0 byte object gives 416 Range Not Satisfiable

RFC 7233 4.4 . 416 Range Not Satisfiable The 416 (Range Not Satisfiable) status code indicates that none of the ranges in the request's Range header field (Section 3.1 )

[ceph-users] Re: RadosGW S3 range on a 0 byte object gives 416 Range Not Satisfiable

On 21.03.2022 15:35, Ulrich Klein wrote: RFC 7233 4.4 . 416 Range Not Satisfiable The 416 (Range Not Satisfiable) status code indicates that none of the ranges in the request's Range header field (Section 3.1

[ceph-users] Re: RadosGW S3 range on a 0 byte object gives 416 Range Not Satisfiable

Yup, completely agree. I find the 416 also a bit surprising, whether in Ceph/RGW or plain HTTP. But I guess it’s just consistent with specifying a range of 1-100 on a one-byte object or any range that can’t be satisfied. After all, the range is part of the request and 4xx means “something wrong w

[ceph-users] Re: RadosGW S3 range on a 0 byte object gives 416 Range Not Satisfiable

On 22.03.2022 09:40, Ulrich Klein wrote: Yup, completely agree. I find the 416 also a bit surprising, whether in Ceph/RGW or plain HTTP. Consistency between other highly used software would be nice. Just to make sure: I am not at all involved in Ceph development, so don’t send a feature requ