Comment 2 for bug 1856303

Thanks a lot for looking into this.

1) I haven't tried any other client as of now. I'll try and provide the trace. But I did try cloudberry with aws s3 and didn't notice any 0 even though Transfer-Encoding chunked header was set

HEAD /readme.txt HTTP/1.1
User-Agent: APN/1.0 CloudBerry Lab/1.0 Explorer/5.9
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20191213T031037Z
Authorization: AWS4-HMAC-SHA256 Credential=AKIAJBKELMZN3VLNRCKA/20191213/us-east-1/s3/aws4_request, SignedHeaders=host;user-agent;x-amz-content-sha256;x-amz-date,Signature=70acab072267d42faa6f61c4cff47bb4456379dde4f8322c41344f5f7158cd39
Host: bhaskartestbucket16052018.s3.amazonaws.com

HTTP/1.1 404 Not Found
x-amz-request-id: 0DF9953EACD70702
x-amz-id-2: ZbxLAXPffPBGxaILWwgpmfRevDaTFTMB82C1Mj1hEjw8MUeCm1HNZGFYYEbOpI6t7rF6PwZTfTI=
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Fri, 13 Dec 2019 03:10:37 GMT
Server: AmazonS3

2) No, I don't think cloudberry is sending any extra header or request metadata. The same set of operation works with AWS s3.

Regards,
Bhaskar