Project

General

Profile

Bug #21128

do not persist aws-chunked content-encoding

Added by Dan van der Ster about 2 years ago. Updated almost 2 years ago.

Status:
Need Review
Priority:
Normal
Target version:
-
Start date:
08/25/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

When an object is PUT with Content-Encoding: aws-chunked, rgw is persisting this header. The result is that when the same object is GET'ed, it has the Content-Encoding: aws-chunked header, even though the content is not encoded. This incorrect header confuses some clients.

The correct behaviour would be to strip aws-chunked from the CE before this is persisted, which is what AWS does. See their doc http://docs.aws.amazon.com/AmazonS3/latest/API/sigv4-streaming.html

S3 will store the resulting object without the aws-chunked encoding. Therefore, when you retrieve the object it will not be aws-chunked encoded.

And by observation AWS does indeed strip it. See the two attached files which show the headers for rgw vs. AWS.

ceph-headers.txt View (3.48 KB) Dan van der Ster, 08/25/2017 02:40 PM

aws-headers.txt View (3.63 KB) Dan van der Ster, 08/25/2017 02:40 PM

History

#2 Updated by Orit Wasserman about 2 years ago

  • Assignee set to Orit Wasserman

#3 Updated by Jos Collin almost 2 years ago

  • Status changed from New to Need Review

Also available in: Atom PDF