)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"0131db05beb6e93be8df38043c3af1bb1ed1ad16","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"db634173_7f4c165d","updated":"2026-08-22 02:02:07.000000000","message":"nope, AWS totally supports transfer-encoding on create bucket (exactly like the existing test says it does)\n\n1001907: sq? Show 927177 rejects AWS-compatible chunked requests | https://review.opendev.org/c/openstack/swift/+/1001907\n\nthe put-object stuff should 501 for sure tho - even sigv2, doesn\u0027t matter what sort of checksum headers you sneak in - we just need to make sure we\u0027re rejecting transfer-encoding: chunked at the right layer to mirror aws compatiblity\n\nwe should NOT \"break\" transfer-encoding: chunked for create bucket or multi-delete POST w/ body, etc - aws supports them just fine and s3api should continue to as well!","commit_id":"67a4f03e42a9d623208529f8cccac16ac275f0e0"},{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"e216ea783e4fd050f3a1e9acc285a7daa0246a97","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"525feae5_8c155194","updated":"2026-08-21 17:40:35.000000000","message":"somewhere we should point to 210646: Accept chunked transfer-encodings | https://review.opendev.org/c/x/swift3/+/210646 as the change that introduced s3api (then swift3) support for this behavior\n\nWe wouldn\u0027t have supported sigv4 or aws-chunked at the time - but the change claims that clients were observed trying to do this, so it\u0027s not clean when/if aws s3 would have rejected those client requests\n\nWe had the idea we should maybe see if the aws s3 behavior/error is any different depending on your signature version?","commit_id":"67a4f03e42a9d623208529f8cccac16ac275f0e0"},{"author":{"_account_id":39146,"name":"Nathaniel Martes","display_name":"Nate Martes","email":"natemartes09@gmail.com","username":"nmartes"},"change_message_id":"9eeba870d5d49f600bcc2d07980f16493c646d05","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"2065ade5_fdff3902","updated":"2026-09-03 18:04:44.000000000","message":"I think this moves us further by adding compat tests for cases, though now we have much more code...","commit_id":"d869af714c0b223ed6a66d9751150590a629a234"}],"test/unit/common/middleware/s3api/test_bucket.py":[{"author":{"_account_id":1179,"name":"Clay Gerrard","email":"clay.gerrard@gmail.com","username":"clay-gerrard"},"change_message_id":"0131db05beb6e93be8df38043c3af1bb1ed1ad16","unresolved":true,"context_lines":[{"line_number":289,"context_line":""},{"line_number":290,"context_line":"    def test_bucket_PUT_chunked_transfer(self):"},{"line_number":291,"context_line":"        # Apparently some clients will include a chunked transfer-encoding"},{"line_number":292,"context_line":"        # even with no body"},{"line_number":293,"context_line":"        req \u003d Request.blank(\u0027/bucket\u0027,"},{"line_number":294,"context_line":"                            environ\u003d{\u0027REQUEST_METHOD\u0027: \u0027PUT\u0027},"},{"line_number":295,"context_line":"                            headers\u003d{\u0027Authorization\u0027: \u0027AWS test:tester:hmac\u0027,"}],"source_content_type":"text/x-python","patch_set":4,"id":"df56f89c_1fcde01c","side":"PARENT","line":292,"updated":"2026-08-22 02:02:07.000000000","message":"bro this test is already explicitly \"test bucket PUT chunked transfer\" - like why didn\u0027t we just try this against AWS before we decided 501 is correct?\n\n1001907: sq? Show 927177 rejects AWS-compatible chunked requests | https://review.opendev.org/c/openstack/swift/+/1001907","commit_id":"e19c896da0eeaf09419726106c46acc3e8bdce39"}]}