Back to bug 2186760

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2023-04-14 11:09:51 UTC Link ID Red Hat Issue Tracker RHCEPH-6458
Mark Kogan 2023-04-14 11:10:41 UTC Target Release 5.3z2 6.1
Mark Kogan 2023-04-14 11:13:42 UTC Status NEW MODIFIED
Mark Kogan 2023-04-14 11:15:08 UTC Assignee mbenjamin mkogan
Veera Raghava Reddy 2023-04-14 19:33:24 UTC Fixed In Version ceph-17.2.6-19.el9cp
Flags needinfo?(mkasturi)
Flags needinfo?(vereddy)
CC vereddy
Flags needinfo?(mkasturi) needinfo?(vereddy)
errata-xmlrpc 2023-04-14 23:49:47 UTC Status MODIFIED ON_QA
Hemanth Sai 2023-04-17 06:10:39 UTC QA Contact mkasturi hmaheswa
Hemanth Sai 2023-04-19 07:26:45 UTC Status ON_QA VERIFIED
Akash Raj 2023-05-04 05:33:08 UTC Docs Contact akraj
Flags needinfo?(mkogan)
Mark Kogan 2023-05-09 15:12:31 UTC Flags needinfo?(mkogan)
Doc Type If docs needed, set a value Bug Fix
Doc Text Cause:
S3 clients that PUT objects with Transfer-Encoding:chunked without providing 'x-amz-decoded-content-length' field would fail

Consequence:
The S3 PUT requests would fail with '411 Length Required' http status code.

Fix:
Do not require that S3 PUT requests with chunked Transfer-Encoding specify a content-length

Result:
S3 client can perform S3 PUT requests with 'chunked' Transfer-Encoding without specifying a Content-Length header
Akash Raj 2023-05-19 11:43:44 UTC Doc Text Cause:
S3 clients that PUT objects with Transfer-Encoding:chunked without providing 'x-amz-decoded-content-length' field would fail

Consequence:
The S3 PUT requests would fail with '411 Length Required' http status code.

Fix:
Do not require that S3 PUT requests with chunked Transfer-Encoding specify a content-length

Result:
S3 client can perform S3 PUT requests with 'chunked' Transfer-Encoding without specifying a Content-Length header
.S3 PUT requests with chunked Transfer-Encoding does not require `content-length`

Previously, S3 clients that PUT objects with `Transfer-Encoding:chunked`, without providing the `x-amz-decoded-content-length` field, would fail. As a result, the S3 PUT requests would fail with `411 Length Required` http status code.

With this fix, S3 PUT requests with chunked Transfer-Encoding need not specify a `content-length`, and S3 clients can perform S3 PUT requests as expected.
Akash Raj 2023-05-19 11:54:03 UTC Blocks 2192813
errata-xmlrpc 2023-06-15 09:08:33 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-06-15 09:17:19 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-06-15 09:17:19 UTC

Back to bug 2186760