Project

General

Profile

Actions

Bug #50115

closed

S3 event message eTag misspelled

Added by Tom Schoonjans about 3 years ago. Updated over 2 years ago.

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

0%

Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
4 - irritation
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

An S3 object event contains its eTag, currently spelled as 'etag' in the message structure, which does not correspond to the documentation example (https://docs.ceph.com/en/latest/radosgw/notifications/#events), or what is used by AWS (https://docs.aws.amazon.com/AmazonS3/latest/userguide/notification-content-structure.html).

The fix appears to be trivial (https://github.com/ceph/ceph/blob/88cc6f22315c8d205d6d0875ad35f92399cd5631/src/rgw/rgw_pubsub.cc#L277), and I am certainly willing to open a pull request for this. However, I wonder if the old spelling should also be kept in the event message structure in order not to break code that relies on this misspelling.


Related issues 1 (0 open1 closed)

Copied to rgw - Backport #51045: pacific: S3 event message eTag misspelledResolvedYuval LifshitzActions
Actions

Also available in: Atom PDF