Bug #12950: rgw: empty etag HTTP header is appended in some cases - rgw - Ceph

Actions

Copy link

Bug #12950

closed

rgw: empty etag HTTP header is appended in some cases

Added by Radoslaw Zarzynski over 8 years ago. Updated about 4 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Radoslaw Zarzynski

Target version:

% Done:

Source:

other

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

It looks that in some circumstances (eg. putting en empty object through Swift API without chunked transfer encoding nor Content-Length specified) radosgw returns etag with an empty value.

$ curl -i "$publicURL/cont/obj" -X PUT -H "X-Auth-Token: $token"

HTTP/1.1 411 Length Required
etag:
Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT
X-Trans-Id: tx000000000000000000005-0055e98e9a-102d-default
Content-Length: 20
Accept-Ranges: bytes
Content-type: text/plain; charset=utf-8
Date: Fri, 04 Sep 2015 12:29:14 GMT

Swift in similar cases just skip the etag header:

$ curl -i "$publicURL/cont/obj" -X PUT -H "X-Auth-Token: $token"

HTTP/1.1 411 Length Required
Content-Length: 75
Content-Type: text/html; charset=UTF-8
X-Trans-Id: tx70bab9c54ffd4afb8aaeb-0055e98ebe
Date: Fri, 04 Sep 2015 12:29:50 GMT

<html><h1>Length Required</h1><p>Content-Length header required.</p></html>