Project

General

Profile

Actions

Bug #24317

closed

rgw: request with range defined as "bytes=0--1" returns 416 InvalidRange

Added by Matt Benjamin almost 6 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
mimic, luminous, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Client application issues an S3 request with range defined as "bytes=0--1". The RadosGW will respond with 416 InvalidRange. AWS S3 will simply ignore the range and provide the whole object.


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #24352: mimic: rgw: request with range defined as "bytes=0--1" returns 416 InvalidRangeResolvedPrashant DActions
Copied to rgw - Backport #24353: luminous: rgw: request with range defined as "bytes=0--1" returns 416 InvalidRangeResolvedMatt BenjaminActions
Copied to rgw - Backport #24354: jewel: rgw: request with range defined as "bytes=0--1" returns 416 InvalidRangeRejectedMatt BenjaminActions
Actions

Also available in: Atom PDF