Bug #2961
rgw: bad content range
0%
Description
Partial download of large file (> 4G), the content range is bad:
2012-08-17 20:28:46.373344 7f29ec7c8700 10 --> Content-Range: bytes 0--6553601 2012-08-17 20:28:46.373348 7f29ec7c8700 10 --> Content-Length: 4288413696
Associated revisions
rgw: dump content_range using 64 bit formatters
Fixes: #2961
Also make sure that size is 64 bit.
backport: argonaut
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
Reviewed-by: Sage Weil <sage@inktank.com>
rgw: dump content_range using 64 bit formatters
Fixes: #2961
Also make sure that size is 64 bit.
backport: argonaut
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
Reviewed-by: Sage Weil <sage@inktank.com>
rgw: dump content_range using 64 bit formatters
Fixes: #2961
Also make sure that size is 64 bit.
backport: argonaut
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
rgw: dump content_range using 64 bit formatters
Fixes: #2961
Also make sure that size is 64 bit.
backport: argonaut
Signed-off-by: Yehuda Sadeh <yehuda@inktank.com>
History
#1 Updated by Sage Weil over 11 years ago
- Target version set to Ceph - v0.51
#2 Updated by Sage Weil over 11 years ago
- Status changed from New to Resolved
#3 Updated by Sage Weil over 11 years ago
- Status changed from Resolved to In Progress
Can we add an s3tests for this?
#4 Updated by Yehuda Sadeh over 11 years ago
it only with >4G objects. A test like that would just take too long. Maybe it's possible to put it as an optional test that doesn't run by default?
#5 Updated by Sage Weil over 11 years ago
- Status changed from In Progress to Resolved
- Backport set to argonaut