Project

General

Profile

Bug #20665

STREAMING-AWS4-HMAC-SHA256-PAYLOAD fails with 0 byte upload

Added by Sendu Bala over 6 years ago. Updated over 6 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I am using RGW Jewel, 10.2.3-0ubuntu0.16.04.2.

I believe this version came out after STREAMING-AWS4-HMAC-SHA256-PAYLOAD was added.

I am trying to use minio-go to put a 0 byte file using this signature type.

As discussed in https://github.com/minio/minio-go/issues/723 , this happens:

PUT /sb10/test.upload HTTP/1.1
Host: cog.sanger.ac.uk
User-Agent: Minio (linux; amd64) minio-go/3.0.0
Content-Length: 0
Authorization: AWS4-HMAC-SHA256 Credential=**REDACTED**/20170714/us-east-1/s3/aws4_request,SignedHeaders=content-encoding;host;x-amz-content-sha256;x-amz-date;x-amz-decoded-content-length,Signature=**REDACTED**
Content-Encoding: aws-chunked
Content-Type: application/csv
X-Amz-Content-Sha256: STREAMING-AWS4-HMAC-SHA256-PAYLOAD
X-Amz-Date: 20170714T154154Z
X-Amz-Decoded-Content-Length: 0
Accept-Encoding: gzip
2017/07/14 15:41:54 Unsolicited response received on idle HTTP channel starting with "HTTP/1.1 400 Bad Request\r\nContent-Length: 122\r\nDate: Fri, 14 Jul 2017 15:41:54 GMT\r\nConnection: close\r\n\r\n"; err=<nil>
HTTP/1.1 411 Length Required
Content-Length: 228
Accept-Ranges: bytes
Content-Type: application/xml
Date: Fri, 14 Jul 2017 15:41:54 GMT
X-Amz-Request-Id: tx0000000000000000bd8e0-005968e642-48581d3-default
<?xml version="1.0" encoding="UTF-8"?>&lt;Error&gt;&lt;Code&gt;MissingContentLength&lt;/Code&gt;&lt;BucketName&gt;sb10&lt;/BucketName&gt;&lt;RequestId&gt;tx0000000000000000bd8e0-005968e642-48581d3-default&lt;/RequestId&gt;&lt;HostId&gt;48581d3-default-default&lt;/HostId&gt;&lt;/Error&gt;

Is this a bug in minio-go, or RGW?

History

#1 Updated by Matt Benjamin over 6 years ago

  • Status changed from New to In Progress
  • Assignee set to Marcus Watts

@sendu, probably RGW but we will root cause

matt

Also available in: Atom PDF